Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.abhiyoheswaran1/projscan

NPM · PROJSCAN · SCANNED AUG 3

Agent-first MCP. 11 AST adapters, 12 named languages, 51 tools, mission outcomes. Local.

Available components

+27 this week 78 Trust /100
Trust breakdown (6 categories)

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 Security88
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 42 of 42 dependencies flagged as unhealthy (42 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to abhiyoheswaran1/projscan). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 14 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 9158 tokens (~160/item across 57 items; 51 tools + 6 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
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

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 · projscan

# add to Claude Code
claude mcp add abhiyoheswaran1-projscan -- npx -y projscan
# add to Codex CLI
codex mcp add abhiyoheswaran1-projscan -- npx -y projscan
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "abhiyoheswaran1-projscan": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "projscan"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add abhiyoheswaran1-projscan --command npx --arg -y --arg projscan
# ~/.hermes/config.yaml
mcp_servers:
  abhiyoheswaran1-projscan:
    command: "npx"
    args: ["-y", "projscan"]
// mcp.json
{
  "mcpServers": {
    "abhiyoheswaran1-projscan": {
      "command": "npx",
      "args": [
        "-y",
        "projscan"
      ]
    }
  }
}
Changelog

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 +72
    • Provenance: unverified → pass security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: abhiyoheswaran1/projscan security
    • MCP protocol: unverified → fail functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → 0.00 functional
    • Maintenance: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → 100 functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 1 Aug 26 −28
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 51

    First indexed and scored.

Diagnostics

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 verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
abhiyoheswaran1/projscan
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/abhiyoheswaran1/projscan/.github/workflows/release.yml@refs/tags/v5.0.3
Rekor log index:
2203630458
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:610758e21f2bf8bde8f0b38af75d75d0df123ca17946fda5f56e019cf6876fdb60e4afc6e7306c99cbf50ef6d1ee6b6594ee6dc78d8dc5d34abd7e2ee
Discovery method:
attestation_endpoint
Dependencies 42 packages

42 packages in the resolved dependency tree · 42 deprecated · 15 stale.

MCP tools — 51 exposed · ~9,037 tokens

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.

Tool Tokens
projscan_workspaces ~82

List monorepo workspace packages (npm/yarn workspaces, pnpm-workspace.yaml, Nx/Turbo/Lerna fallback). Returns one row per package with name, relative path, and version. Use the package `name` as the `package` argument on projscan_hotspots / projscan_coupling to scope those tools to a single package.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.