Loading the registry…
Enhanced MCP server-memory with ZeroDB cloud persistence and semantic vector search. Drop-in replacement for @modelcontextprotocol/server-memory that stores your knowledge graph in the cloud instead of local JSONL files.
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
npm: ainative-memory-mcp @ 1.0.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- ainative-memory-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.9s
v2.0.11
20 findings · 6.3s
v0.3.74
5 findings · 0.9s
v0.2.0
10 findings · 3.6s
v0.2.0
0 findings · 3.6s
v0.1.0
0 findings · 9.6s
v0.71.0
34 findings · 0.3s
v2.3.8
34 findings · 6.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged37 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 1, 2026 | Flagged32 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-scanner: complete | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 103 findings across every scanner that examined this package.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
10 DATA_EXFIL_JS_NETWORK
Files: /repo/index.js · reported by cisco-skill-scanner
10 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/index.js · reported by nerlo-behavioral
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/.claude/SKILL.md, /repo/.cody/SKILL.md · reported by cisco-skill-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/.claude/SKILL.md, /repo/.cody/SKILL.md · reported by cisco-skill-scanner
2 GHSA-frvp-7c67-39w9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 MANIFEST_INVALID_NAME
Files: /repo/.cody/SKILL.md, /repo/.claude/SKILL.md · reported by cisco-skill-scanner
1 AAK-ANTHROPIC-SDK-001
Files: index.js · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: index.js · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: index.js · reported by agent-audit-kit
1 CVE-2026-12143
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-13676
Files: package-lock.json · reported by trivy
1 CVE-2026-16221
Files: package-lock.json · reported by trivy
1 CVE-2026-18446
Files: package-lock.json · reported by trivy
1 CVE-2026-54272
Files: package-lock.json · reported by trivy
1 CVE-2026-59895
Files: package-lock.json · reported by trivy
1 CVE-2026-59896
Files: package-lock.json · reported by trivy
1 CVE-2026-59897
Files: package-lock.json · reported by trivy
1 CVE-2026-67312
Files: package-lock.json · reported by trivy
1 CVE-2026-67313
Files: package-lock.json · reported by trivy
1 CVE-2026-67314
Files: package-lock.json · reported by trivy
1 CVE-2026-67315
Files: package-lock.json · reported by trivy
1 CVE-2026-67316
Files: package-lock.json · reported by trivy
1 CVE-2026-67317
Files: package-lock.json · reported by trivy
1 CVE-2026-67318
Files: package-lock.json · reported by trivy
1 CVE-2026-67319
Files: package-lock.json · reported by trivy
1 CVE-2026-67320
Files: package-lock.json · reported by trivy
1 CVE-2026-67321
Files: package-lock.json · reported by trivy
1 CVE-2026-69192
Files: package-lock.json · reported by trivy
1 CVE-2026-69198
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
Files: package-lock.json · reported by trivy
1 CVE-2026-71848
Files: package-lock.json · reported by trivy
1 CVE-2026-71849
Files: package-lock.json · reported by trivy
1 CVE-2026-71850
Files: package-lock.json · reported by trivy
1 CVE-2026-75899
Files: package-lock.json · reported by trivy
1 CVE-2026-76172
Files: package-lock.json · reported by trivy
1 CVE-2026-82417
Files: package-lock.json · reported by trivy
1 CVE-2026-82562
Files: package-lock.json · reported by trivy
1 CVE-2026-84363
Files: package-lock.json · reported by trivy
1 CVE-2026-84364
Files: package-lock.json · reported by trivy
1 CVE-2026-84365
Files: package-lock.json · reported by trivy
1 GHSA-22jq-vg5j-6vgg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4mjr-xmp4-gh2g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4xrf-jv44-h6hh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-crvj-82cr-hjcx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f4gw-2p7v-4548
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f65p-4m7j-42xc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fph4-wmhf-6fwf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g6gw-c38x-mqfc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-gcfj-64vw-6mp9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-gqvv-2mrq-wpjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hcpx-6fm6-wx23
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hvrm-45r6-mjfj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqff-g426-hqxp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqh4-m9w3-8hp9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mmx7-hfxf-jppx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mwf2-3pr3-8698
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w62v-xxxg-mg59
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-x5fp-wj9c-mxmx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xj6q-8x83-jv6g
Files: /repo/package-lock.json · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.cody/CODY.md · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-75975
Files: package-lock.json · reported by trivy
Artifact has credential access, network egress, and supply chain vulnerabilities.
The artifact exhibits multiple instances of credential access and network egress in `index.js`, specifically handling secrets and performing network operations. It also contains high-severity vulnerabilities related to Anthropic SDK and Splunk token logging in `index.js`. Additionally, several high-severity supply chain vulnerabilities are present in dependencies listed in `package-lock.json`.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 25 of 30; the rest are in the per-scanner reports above.