Packkit
NPM · PACKKIT-MCP · SCANNED AUG 3
Scaffold modern npm packages, CLIs, services and apps as a native tool for AI agents.
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 Security63
- No malware found by supply-chain analysis.Pass
- CVE data not yet available for this package.Unverified
- No install/post-install scripts declared.Pass
- Dependency-health data not yet available.Unverified
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to PackkitJS/create-packkit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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 · packkit-mcp
claude mcp add packkitjs-packkit-mcp -- npx -y packkit-mcp
codex mcp add packkitjs-packkit-mcp -- npx -y packkit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"packkitjs-packkit-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"packkit-mcp"
],
"enabled": true
}
}
} openclaw mcp add packkitjs-packkit-mcp --command npx --arg -y --arg packkit-mcp
mcp_servers:
packkitjs-packkit-mcp:
command: "npx"
args: ["-y", "packkit-mcp"] {
"mcpServers": {
"packkitjs-packkit-mcp": {
"command": "npx",
"args": [
"-y",
"packkit-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 38
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 verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- PackkitJS/create-packkit
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/PackkitJS/create-packkit/.github/workflows/release.yml@refs/heads/main
- Rekor log index:
- 2331882801
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:f5615138ce96df565698cef0892f6507d3431750848d2d21e9128ca5185cbfd39fdc15799d9c4ca93f414013734f7a60ff4ddcb2701f65e2b10f3bfee
- Discovery method:
- attestation_endpoint
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.
packkit_preview ~140
Show the project structure a config would produce — the full file tree and stack summary — without writing anything. Use this to check the layout before committing to it, and to show the user what they are about to get. Cheap and side-effect free, so prefer it over scaffolding to a throwaway directory to see what happens.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name |
| options | object | — | Any options from packkit_schema (e.g. { "framework": "vue", "target": ["library"] }) |
| preset | string | — | A preset or alias (e.g. ts-lib, react-lib, node-service, rlib) |
No output schema declared.
No examples provided.
packkit_scaffold ~274
Generate a project to disk. Writes files under <directory>/<name> (or ./<name>), optionally runs git init, installs dependencies, and creates the GitHub repository. Call packkit_schema first if you have not already — picking the preset by guess is how projects end up the wrong shape. If the target directory already has files in it (an existing clone, for instance), pass merge: true rather than failing.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | — | Parent directory to create the project in (default: current working directory) |
| git | boolean | — | git init + initial commit (default false) |
| github | boolean | — | Create the repository on GitHub and push to it, using the `gh` CLI. Requires git. Private unless "public" is set. |
| install | boolean | — | Install dependencies (default false) |
| merge | boolean | — | Scaffold into a non-empty directory. Existing files are never overwritten — colliding ones are skipped and reported. Use this when the target is an already-cloned repo. |
| name | string | yes | Package name (also the folder name) |
| options | object | — | Any options from packkit_schema |
| preset | string | — | A preset or alias |
| public | boolean | — | When creating the repository, make it public (default: private) |
No output schema declared.
No examples provided.
packkit_schema ~82
START HERE. Returns every Packkit option, preset, and shortcut alias as JSON. Call this before scaffolding so you pick a preset that matches what the user actually wants — presets range from single libraries to CLIs, HTTP services, SPAs, and full-stack monorepos, and guessing without reading them is the main cause of scaffolding the wrong shape.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.