Loading the registry…
Neutral freight reference + validation layer for AI agents — ADR dangerous goods, HS codes, airlines, airports, UN/LOCODE, Incoterms, identifier validation and freight math. Every tool declares a typed output schema and returns a source-cited response envelope (structuredContent) an agent can cite.
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: freightutils-mcp @ 2.12.3, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- freightutils-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.5s
v2.0.11
11 findings · 6.7s
v0.3.26
10 findings · 0.9s
v0.1.0
4 findings · 27.3s
v0.1.0
0 findings · 27.3s
v0.1.0
0 findings · 17.6s
v0.71.0
32 findings · 0.4s
v2.3.8
32 findings · 6.9s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
No report in this scan: capslock, govulncheck.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 4, 2026 | Flagged37 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·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 89 findings across every scanner that examined this package.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
3 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: MANIFEST_INVALID_NAME, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/.github/ISSUE_TEMPLATE/SKILL.md · reported by cisco-skill-scanner
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: FILE_MAGIC_MISMATCH, AAK-HEALTHCARE-AI-004 · Files: /repo/.github/workflows/publish-registry.yml, .github/workflows/publish-registry.yml · reported by cisco-skill-scanner, agent-audit-kit
1 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-SECRET-004 · Files: src/api.test.ts · reported by agent-audit-kit
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/src/api.ts, /repo/src/ping.ts · reported by cisco-skill-scanner
4 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/api.ts, /repo/src/ping.ts · reported by nerlo-behavioral
2 AAK-MCP-018
Files: src/server.ts, src/ping.ts · reported by agent-audit-kit
2 AAK-SECRET-004
Files: src/api.ts, src/ping.ts · reported by agent-audit-kit
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
1 AAK-ANTHROPIC-SDK-001
Files: src/bin/cli.ts · reported by agent-audit-kit
1 AAK-HEALTHCARE-AI-004
Files: README.md · 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-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-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-42338
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-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-59896
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-8723
Files: package-lock.json · reported by trivy
1 GHSA-2gcr-mfcq-wcc3
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-69xw-7hcm-h432
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-92pp-h63x-v22m
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-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-hvrm-45r6-mjfj
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-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-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-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-v2v4-37r5-5v8g
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-w62v-xxxg-mg59
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 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
Artifact handles secrets, performs network egress, and has high-severity vulnerabilities.
The artifact handles secrets in `src/api.ts` and `src/ping.ts`, which are then used in network egress operations from these same files. It also uses an Anthropic SDK in `src/bin/cli.ts`, indicating potential external communication. Furthermore, the artifact contains multiple high-severity vulnerabilities in its dependencies, identified by `trivy` and `osv-scanner` 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.