Loading the registry…
Power your chat with B2B data to create lead lists, research companies, personalize your outreach, and more.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- vibe-prospecting
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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.5s
v2.0.11
2 findings · 6.6s
v0.3.74
1 finding · 0.7s
v0.1.0
0 findings · 2.7s
v0.1.0
0 findings · 2.7s
v0.71.0
49 findings · 0.2s
v2.3.8
49 findings · 7.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.0s
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 3, 2026 | Flagged49 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 12, 2026 | Flagged49 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | 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 101 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.
2 GHSA-26pp-8wgv-hjvm
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-frvp-7c67-39w9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-gq3j-xvxp-8hrf
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-v8w9-8mx6-g223
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2025-69873
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-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-24398
Files: package-lock.json · reported by trivy
1 CVE-2026-24472
Files: package-lock.json · reported by trivy
1 CVE-2026-24473
Files: package-lock.json · reported by trivy
1 CVE-2026-24771
Files: package-lock.json · reported by trivy
1 CVE-2026-25536
Files: package-lock.json · reported by trivy
1 CVE-2026-29045
Files: package-lock.json · reported by trivy
1 CVE-2026-29085
Files: package-lock.json · reported by trivy
1 CVE-2026-29086
Files: package-lock.json · reported by trivy
1 CVE-2026-29087
Files: package-lock.json · reported by trivy
1 CVE-2026-39406
Files: package-lock.json · reported by trivy
1 CVE-2026-39407
Files: package-lock.json · reported by trivy
1 CVE-2026-39408
Files: package-lock.json · reported by trivy
1 CVE-2026-39409
Files: package-lock.json · reported by trivy
1 CVE-2026-39410
Files: package-lock.json · reported by trivy
1 CVE-2026-44455
Files: package-lock.json · reported by trivy
1 CVE-2026-44456
Files: package-lock.json · reported by trivy
1 CVE-2026-44457
Files: package-lock.json · reported by trivy
1 CVE-2026-44458
Files: package-lock.json · reported by trivy
1 CVE-2026-44459
Files: package-lock.json · reported by trivy
1 CVE-2026-47673
Files: package-lock.json · reported by trivy
1 CVE-2026-47674
Files: package-lock.json · reported by trivy
1 CVE-2026-47675
Files: package-lock.json · reported by trivy
1 CVE-2026-47676
Files: package-lock.json · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-54286
Files: package-lock.json · reported by trivy
1 CVE-2026-54287
Files: package-lock.json · reported by trivy
1 CVE-2026-54288
Files: package-lock.json · reported by trivy
1 CVE-2026-54289
Files: package-lock.json · reported by trivy
1 CVE-2026-54290
Files: package-lock.json · reported by trivy
1 CVE-2026-56761
Files: package-lock.json · reported by trivy
1 CVE-2026-59895
Files: package-lock.json · reported by trivy
1 CVE-2026-59897
Files: package-lock.json · reported by trivy
1 CVE-2026-6321
Files: package-lock.json · reported by trivy
1 CVE-2026-6322
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
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-8723
Files: package-lock.json · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2gcr-mfcq-wcc3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3hrh-pfw6-9m5x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-458j-xx4x-4375
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-5pq2-9x2x-5p6w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-69xw-7hcm-h432
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6wqw-2p9w-4vw4
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-88fw-hqm2-52qc
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-92pp-h63x-v22m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9r54-q6cx-xmh5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9vqf-7f2p-gf9v
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-f577-qrjj-4474
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hm8q-7f3q-5f36
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p6xx-57qc-3wxr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p77w-8qqv-26rm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q3j6-qgpj-74h6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q5qw-h33p-qvwr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qp7p-654g-cw7p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r354-f388-2fhh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r5rp-j6wh-rvv4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
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-v39h-62p7-jpjc
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-w332-q679-j88p
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-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wc8c-qw6v-h7f6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wmmm-f939-6g9c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xf4j-xp2r-rqqx
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-xpcf-pg52-r92g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xrhx-7g5j-rcj5
Files: /repo/package-lock.json · reported by osv-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Multiple high-severity vulnerabilities found in dependencies.
This artifact contains numerous high-severity vulnerabilities identified in its dependencies, primarily listed in `package-lock.json`. These vulnerabilities could potentially enable remote code execution, data access, or denial of service. Reviewing these dependency issues is critical before deployment.
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.