2 checks that ran failed — permission scope and version behavior — so this release can’t be trusted as-is.
- Publisher
- io.github.abhiyoheswaran1
- Repository
- github.com/abhiyoheswaran1/projscan
- Install
- npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan, npm:projscan
- Versions
- 62
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-07-20 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
repository linkage verified
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
Reads secrets from the environment (e.g. scripts/capture-vhs-demos.mjs) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
fail15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
HIGH: shell/exec capability AND destructive filesystem writes together (scripts/capture-readme-assets.mjs: imports child_process and calls exec/spawn; docs/examples/plugins/monorepo-boundary.mjs: path traversal ('../') combined with file access). discloses shell/exec capability: scripts/capture-readme-assets.mjs: imports child_process and calls exec/spawn discloses shell/exec capability: scripts/capture-vhs-demos.mjs: imports child_process and calls exec/spawn discloses broad/destructive filesystem access: docs/examples/plugins/monorepo-boundary.mjs: path traversal ('../') combined with file access Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 5.0.2 (patch bump): new capability primitive(s) in source: child_process.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references TELEMETRY behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v5.0.3 · current | 2026-07-19 | C | 70 | 5/6 · 75% | B→C in v5.0.3 |
| v5.0.2 | 2026-07-14 | B | 82.5 | 5/6 · 75% | ±0 |
| v5.0.1 | 2026-07-13 | B | 82.5 | 4/6 · 65% | — |