io.github.Baneado98/import-guardian
NPM · IMPORT-GUARDIAN-MCP · SCANNED AUG 3
Catch AI-hallucinated (slopsquatted) npm imports in generated code before npm install.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 38 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1346 tokens (~336/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · import-guardian-mcp
claude mcp add baneado98-import-guardian -- npx -y import-guardian-mcp
codex mcp add baneado98-import-guardian -- npx -y import-guardian-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"baneado98-import-guardian": {
"type": "local",
"command": [
"npx",
"-y",
"import-guardian-mcp"
],
"enabled": true
}
}
} openclaw mcp add baneado98-import-guardian --command npx --arg -y --arg import-guardian-mcp
mcp_servers:
baneado98-import-guardian:
command: "npx"
args: ["-y", "import-guardian-mcp"] {
"mcpServers": {
"baneado98-import-guardian": {
"command": "npx",
"args": [
"-y",
"import-guardian-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 42
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 97 packages
97 packages in the resolved dependency tree · 96 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
audit_lockfile ~828
DEEP supply-chain audit of a RESOLVED lockfile — the premium product. Works across NINE ecosystems: npm (package-lock.json v1/v2/v3, yarn.lock classic/berry, pnpm-lock.yaml), Python/PyPI (requirements.txt, poetry.lock, Pipfile.lock), Go (go.mod, go.sum), Rust/Cargo (Cargo.lock, Cargo.toml), Java (Maven pom.xml, Gradle build.gradle/.kts + gradle.lockfile), PHP/Composer (composer.json, composer.lock), Ruby/RubyGems (Gemfile.lock, Gemfile), and .NET/NuGet (packages.lock.json, .csproj/Directory.Packages.props). It resolves the dependency graph and cross-checks each name against that ecosystem's LIVE public index (npm registry, PyPI, the Go module proxy, crates.io, Maven Central, Packagist, rubygems.org, nuget.org), auditing for: (1) DEPENDENCY CONFUSION — internal/private package names unclaimed on the public registry that an attacker can shadow (the highest-impact supply-chain attack), INCLUDING npm SCOPE-SHADOWING (a private @org/pkg whose whole @org scope is unclaimed), Maven groupId confusion, Composer vendor/package confusion, RubyGems private-source gem confusion, and NuGet feed confusion (the ORIGINAL Birsan 2021 vector — an internal package ID not reserved on nuget.org while a private feed is restored alongside it); (2) transitive TYPOSQUATS and homoglyph/Unicode-confusable clones (Damerau-Levenshtein + confusable folding, per-registry canonicalization incl. crates.io -/_ equivalence, Maven/Composer coordinate typos, RubyGems gem typos incl. the rest-client/rest_client class, and NuGet dotted-ID typos); (3) nonexistent pinned packages; (4) MAINTAINER-TAKEOVER fingerprints (dormant package republished, version burst, Packagist-ABANDONED packages, the RubyGems rest-client-hijack pattern); (5) INSTALL-SCRIPT VERSION-DIFFING — a package whose newest release ADDED a preinstall/postinstall/install/prepare hook the previous release did NOT have (the exact injection shape of event-stream / ua-parser-js); (6) INSTALL-SCRIPT PAYLOAD ANALYSIS — downloads the package tarba…
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | — | Optional filename so the ecosystem is detected reliably (e.g. 'pnpm-lock.yaml', 'Cargo.lock', 'go.sum', 'Gemfile.lock', 'packages.lock.json', 'App.csproj'). Defaults to package-lock.json. |
| lockfile | string | yes | The full contents of the lockfile to audit (package-lock.json / yarn.lock / pnpm-lock.yaml / requirements.txt / poetry.lock / Pipfile.lock / go.mod / go.sum / Cargo.lock / Cargo.toml / pom.xml / comp… |
No output schema declared.
No examples provided.
check_packages ~149
Check an explicit list of npm package names for hallucination / slopsquatting (e.g. a dependency list you are about to install). Returns CLEAN / REVIEW / BLOCK per package with a 'did you mean' for fakes. The free tier verifies a small handful (≤5 names); a full dependency manifest or pro=true routes to the premium unlimited batch verify (requires IMPORT_GUARDIAN_KEY).
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | npm package names to verify. |
| pro | boolean | — | Force the PREMIUM unlimited batch verify (runs server-side behind payment). Auto-enabled when the list exceeds the free cap. Requires IMPORT_GUARDIAN_KEY; without one you'll get instructions to unloc… |
No output schema declared.
No examples provided.
scan_code_imports ~285
Scan a block of JS/TS source code for HALLUCINATED / slopsquatted npm imports BEFORE you install anything or commit. Extracts every npm package the code imports/requires and checks each against the live npm registry: flags packages that DO NOT EXIST (AI hallucinations — the #1 slopsquatting attack vector in 2026, where attackers register the plausible fake name to ship malware) and packages that exist but look freshly-squatted (brand-new, no repo, near-typo of a popular lib, near-zero usage). Returns a CLEAN / REVIEW / BLOCK verdict with a 'did you mean' suggestion for each bad import. ALWAYS run this on code you (an AI) just generated before running its install command. The free tier handles a code fragment (≤2,000 chars AND ≤5 distinct imported packages); a whole file / repo dump, more than 5 packages, or pro=true routes to the premium unlimited scan (requires IMPORT_GUARDIAN_KEY).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The JS/TS source code to scan (the code an AI agent just generated). |
| pro | boolean | — | Force the PREMIUM unlimited/batch scan (runs server-side behind payment). Auto-enabled when the code exceeds the free fragment cap. Requires IMPORT_GUARDIAN_KEY; without one you'll get instructions t… |
No output schema declared.
No examples provided.
verify_package ~84
Verify a single npm package name exists and is not a slopsquat: registry existence, age, version history, repo, weekly downloads, and edit-distance to popular packages. Use right before adding a dependency you are not 100% sure is real. Always free.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The npm package name, e.g. 'lodash' or '@scope/pkg'. |
No output schema declared.
No examples provided.