pkgxray
NPM · PKGXRAY
Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.
Available components
Last scanned (19 hours ago)
Scores higher than 94% of npm servers
Category Security
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 → Why this is hard to score →
Supply Chain Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to adamsjack711-ux/pkgxray). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 996 tokens (~249/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 13 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
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 4 Nov 2026 · Analysed npm/pkgxray@1.0.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | adamsjack711-ux/pkgxray |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/adamsjack711-ux/pkgxray/.github/workflows/release.yml@refs/tags/v1.0.5 |
| Rekor log index | 2256768150 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ce7e43f1477ec01d04230fae4c0059dd8eea55e0b404b0e9c10ec95843019da19e1d3bc4362d3753a60475180a8da4fc2524848441a4dcb5631f75d4f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_agent_extension_supply_chain Audit supplied package evidence ~256
Statically analyze caller-supplied package source and metadata. Returns a structured SAFE, REVIEW, or BLOCK report with cited findings; it does not read local files, install packages, or execute code. A SAFE result is defense in depth, not proof of harmlessness. For a live npm package, use guard_agent_extension_install.
| Name | Type | Req | Description |
|---|---|---|---|
| githubMetadata | – | – | – |
| knownVulnerabilities | array | – | Optional array of OSV-shaped vulnerability records (id, aliases, summary, references). |
| npmMetadata | – | – | – |
| npmVsGithubDiff | object | – | Optional pre-computed npm-vs-github file diff (see guard output for shape). |
| outputFormat | string | – | – |
| packageName | string | – | – |
| provenanceAttestation | object | – | Optional npm SLSA provenance attestation object (as returned by registry.npmjs.org/-/npm/v1/attestations). When provided, the auditor cross-checks the attested source repo against the declared packag… |
| sourceFiles | – | yes | Map of file path to source text, or an array of objects with path/name and content/text. |
| webPresence | – | – | – |
No output schema declared.
No examples provided.
audit_lockfile_supply_chain Audit a dependency manifest ~211
Read a dependency manifest under an operator-approved root and query OSV for each resolved dependency. Returns structured SAFE, REVIEW, or BLOCK decisions and honors a sibling .pkgxray.lock; it does not install dependencies or execute package code. deep/deepAll add npm and GitHub network scans.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Run the full guard pipeline (static heuristics + GitHub metadata) on every OSV-blocked dep. Slower but surfaces more bands. |
| deepAll | boolean | – | Run the deep pipeline on every dep, not just blocked ones. Much slower; use sparingly. |
| lockfilePath | string | yes | Path to a package-lock.json, npm-shrinkwrap.json, yarn.lock, pnpm-lock.yaml, or package.json under an operator-approved root. Must be a readable regular file. |
| outputFormat | string | – | – |
| vulnerabilityCheck | boolean | – | Set false to skip the OSV query (useful when offline or pre-supplied). |
No output schema declared.
No examples provided.
guard_agent_extension_install Guard a package before installation ~308
Fetch and stage one package reference (pin an exact version for reproducibility), then return a structured SAFE, REVIEW, or BLOCK report without running lifecycle scripts or package code. It performs network requests to npm, OSV, and optionally GitHub. promoteTo writes files only after policy allows; force may replace an existing destination. Local references and caller-supplied paths are confined to operator-approved roots.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Reserved — guard already runs the full pipeline; passed through for parity with audit_lockfile_supply_chain. |
| force | boolean | – | – |
| githubDiff | boolean | – | Set false to skip the npm-vs-GitHub source diff (saves a tarball download). |
| githubMetadata | boolean | – | Set false to skip the GitHub provenance cross-check. |
| outputFormat | string | – | – |
| policy | string | – | – |
| promoteTo | string | – | Optional destination under an operator-approved root. Files are copied only when policy allows; force can replace an existing destination. |
| quarantineRoot | string | – | Optional staging root under an operator-approved filesystem root. Omit to use an internally selected OS temporary directory. |
| reference | string | yes | Exact package reference, preferably npm:name@version. Local file:path or directory references must resolve under an operator-approved root. |
| sourceScan | boolean | – | Set false to stage and vulnerability-check without collecting source files. |
| vulnerabilityCheck | boolean | – | Set false to skip OSV vulnerability intelligence checks. |
No output schema declared.
No examples provided.
triage_lockfile_supply_chain Record dependency triage decisions ~221
Read a manifest under an operator-approved root and write bulk allow or block decisions to its sibling .pkgxray.lock. This changes future audit policy for every selected dependency: auto=allow suppresses those findings, while auto=block preserves rejection. MCP has no interactive confirmation, so review the target and mode before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| auto | string | yes | Required. Decision to apply to every package in the worklist. 'block' records each flagged dep as blocked (preserves OSV findings as documented suppressions); 'allow' accepts every dep and silences i… |
| includeSafe | boolean | – | If true, every dep (including OSV-safe ones) enters the worklist. Default false — only block/review deps are decided. |
| lockfilePath | string | yes | Path to a package-lock.json, npm-shrinkwrap.json, yarn.lock, pnpm-lock.yaml, or package.json under an operator-approved root. A sibling .pkgxray.lock will be written. |
| outputFormat | string | – | – |
No output schema declared.
No examples provided.
How do I install the pkgxray MCP server?
pkgxray runs locally as an npm package, launched with npx -y pkgxray. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pkgxray
claude mcp add adamsjack711-ux-pkgxray -- npx -y pkgxray
What is the pkgxray MCP server?
pkgxray is an MCP server listed in the public MCP registry as io.github.adamsjack711-ux/pkgxray. Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence. This page covers its npm package (pkgxray).
Is the pkgxray MCP server safe to use?
pkgxray scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the pkgxray MCP server expose?
pkgxray exposes 4 tools: audit_agent_extension_supply_chain, guard_agent_extension_install, audit_lockfile_supply_chain, triage_lockfile_supply_chain. Their descriptions and schemas cost roughly 996 tokens of context every time the server is loaded.
Is the pkgxray MCP server still maintained?
pkgxray is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the pkgxray MCP server under?
pkgxray declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.