# npm pack checker (what npm publish ships) (mcpb · npm-pack-check-1.0.0.mcpb)

Exact files npm publish ships, which rule decides each, and leaks (.env, keys) to fix first.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `npm-pack-check-1.0.0.mcpb`: 38/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check.md), [page](https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check)
- oci · `ghcr.io/lawatch/npm-pack-check`: 40/100, [markdown](https://verifymcp.io/servers/lawatch-npm-pack-check/ghcr-io-lawatch-npm-pack-check.md), [page](https://verifymcp.io/servers/lawatch-npm-pack-check/ghcr-io-lawatch-npm-pack-check)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Lawatch/10aday/releases/download/npm-pack-check-v1.0.0/npm-pack-check-1.0.0.mcpb`
- Transport: `stdio`
- SHA-256: `1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 778 tokens (~389/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the npm pack checker (what npm publish ships) MCP server?

npm pack checker (what npm publish ships) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Lawatch/10aday/releases/download/npm-pack-check-v1.0.0/npm-pack-check-1.0.0.mcpb`
- SHA-256: `1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743`

### Verify on macOS / Linux

```bash
echo "1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743  npm-pack-check-1.0.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\npm-pack-check-1.0.0.mcpb).Hash -eq "1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-16 (score 38)

First indexed and scored.

## MCP tools (2)

### `check_npm_pack` (~370 tokens)

Which files will npm publish ship?

Gives the exact file list that `npm pack` / `npm publish` puts in the tarball (npm 10 rules, same order as npm), what is left out, and the warnings that matter before publishing: secrets or .env files that would be published, a .npmignore that silently replaces .gitignore (so git-ignored files get published), "files" entries that match nothing, "main"/"bin"/"browser" pointing to a file that will not be in the package, tests and coverage shipped by mistake. Use it before any publish, when a published package misses files ("Cannot find module" after install) or ships too much. No disk access needed: pass package.json, the file list and the ignore files.

Input parameters:

- `explain` (array): Optional: paths to explain one by one (included or not, and which rule decides).
- `ignore_files` (object): Content of every .npmignore and .gitignore, at any depth, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "lib/.npmignore": "..." }. They are added to the file list automatically.
- `list_excluded` (boolean): Also return the list of excluded files (default false: only the count by top folder).
- `package_json` (object|string, required): The root package.json, as an object or as JSON text.
- `paths` (array, required): Every file of the project, relative to the package root, "/" separators. Best: the output of `git ls-files --cached --others` plus untracked build output (e.g. `find . -type f -not -path "./node_modu…

Output parameters:

- `excluded` (array)
- `excluded_by_folder` (object)
- `excluded_count` (integer)
- `explained` (array)
- `included` (array): Files in the tarball, in npm order.
- `included_count` (integer)
- `warnings` (array)

### `why_npm_pack` (~279 tokens)

Why is this file (not) in my npm package?

For each path asked, says whether `npm publish` ships it and which exact rule decides: the line of .npmignore or .gitignore (with file and line number), the "files" entry of package.json, or npm's built-in rules (README/LICENSE/package.json always shipped, node_modules/.git/.npmrc/lockfiles never, "main" and "bin" forced in). Also says when a whole folder was skipped.

Input parameters:

- `explain` (array, required): Paths to explain (they are added to the file list if missing).
- `ignore_files` (object): Content of every .npmignore and .gitignore, at any depth, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "lib/.npmignore": "..." }. They are added to the file list automatically.
- `package_json` (object|string, required): The root package.json, as an object or as JSON text.
- `paths` (array): Every file of the project, relative to the package root, "/" separators. Best: the output of `git ls-files --cached --others` plus untracked build output (e.g. `find . -type f -not -path "./node_modu…

Output parameters:

- `explained` (array)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check#diagnostics

## Score history

- 2026-11-21: 38
- 2026-11-20: 38
- 2026-11-19: 38
- 2026-11-18: 38
- 2026-11-17: 38
- 2026-11-16: 38

## Common questions

### What is the npm pack checker (what npm publish ships) MCP server?

npm pack checker (what npm publish ships) is an MCP server listed in the public MCP registry as io.github.Lawatch/npm-pack-check. Exact files npm publish ships, which rule decides each, and leaks (.env, keys) to fix first. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/npm-pack-check-v1.0.0/npm-pack-check-1.0.0.mcpb).

### Is the npm pack checker (what npm publish ships) MCP server safe to use?

npm pack checker (what npm publish ships) scores 38 out of 100 on VerifyMCP. 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 npm pack checker (what npm publish ships) MCP server expose?

npm pack checker (what npm publish ships) exposes 2 tools: check_npm_pack, why_npm_pack. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### What licence is the npm pack checker (what npm publish ships) MCP server under?

npm pack checker (what npm publish ships) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the npm pack checker (what npm publish ships) MCP server?

VerifyMCP ran 11 checks on npm pack checker (what npm publish ships), covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about npm pack checker (what npm publish ships): Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-npm-pack-check/npm-pack-check
