gm-plugkit@2.0.2468
Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform wasm, verifies SHA256, and launches agentplug-runner (the native wasm host) as the spool watcher daemon.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package has a concrete, persistent AI-agent control surface and executes a remotely updated native component, but source inspection found no lifecycle hook, credential theft, or other concrete malicious payload. This meets the explicit-user-command agent-config mutation warning boundary.
Decision evidence
public snapshot- bootstrap.js:571-640 installs bundled skill files into ~/.agents/skills and ~/.claude/skills.
- SKILL-gm-continue.md requires repeated agent dispatches and discourages deferring to the user.
- bootstrap-shared.js:251-289 creates/edits project CLAUDE.md and AGENTS.md to load .gm instructions.
- bootstrap.js:841-878 downloads a native runner, verifies its hash from the same release, and cli.js executes it.
- package.json has no lifecycle scripts; this occurs on explicit CLI/bootstrap use.
- No install, preinstall, or postinstall hook is declared.
- No credential harvesting or data-exfiltration code was found.
- Network targets are package-associated GitHub releases/API and npm registry.
- Project and agent-skill writes are reached through user-invoked CLI/bootstrap paths.
Source & flagged code
4 flagged · loading sourcePackage source references child process execution.
bootstrap-shared.jsView on unpkg · L5Source downloads or fetches remote code and executes it.
bootstrap.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to gm-plugkit@2.0.2468.
See all versions of gm-plugkit for other recorded verdicts.
- Review the evidence and your use of gm-plugkit@2.0.2468 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.