Loading the registry…
IP Intelligence Search Tool
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.
npm: chaitin-ip-intelligence-search-tool @ 0.1.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- chaitin-ip-intelligence-search-tool
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.6s
v2.0.11
7 findings · 6.2s
v0.3.74
6 findings · 1.1s
v0.2.0
0 findings · 3.3s
v0.2.0
0 findings · 3.3s
v0.1.0
0 findings · 8.7s
v0.71.0
23 findings · 0.2s
v2.3.8
39 findings · 6.5s
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
6 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged46 | — | 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 |
| Jul 21, 2026 | Flagged43 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completetrivy: completeosv-scanner: complete | completed |
| Jul 20, 2026 | Flagged38 | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completetrivy: completeosv-scanner: complete | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·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 75 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.
4 DATA_EXFIL_JS_NETWORK
Files: /repo/dist/server.js, /repo/src/server.ts · reported by cisco-skill-scanner
3 CVE-2025-15284
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
3 CVE-2026-2391
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
3 CVE-2026-82417
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
3 CVE-2026-8723
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
3 GHSA-4mjr-xmp4-gh2g
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 AAK-MCP-018
Files: src/index.ts, src/server.ts · reported by agent-audit-kit
2 CVE-2025-66414
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-0621
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-12590
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-4923
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-4926
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · 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 CVE-2025-13466
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-wqch-xfxh-vrr4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-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
High-severity vulnerabilities and network risks identified.
The artifact contains multiple high-severity vulnerabilities in its dependencies, as indicated by various GHSA and CVE findings in lock files. It exhibits DNS rebinding behavior in `package.json`, which can lead to network egress risks. Additionally, the artifact uses the Anthropic SDK in `src/index.ts`, potentially involving external API calls and data transmission. Several medium and low severity vulnerabilities are also present across its dependencies.
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 26; the rest are in the per-scanner reports above.