@keemgunn/lanesmith
A personal Git workflow CLI for repo onboarding, branching, Release Lane Models, and release workflows.
This report shows the evidence for @keemgunn/lanesmith@1.4.0. 1 of 3 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a concrete, automatic postinstall path that mutates third-party AI-agent control surfaces in the user's home directory. Although no credential theft or network exfiltration was found, this unconsented lifecycle behavior meets the install-control-surface blocking policy.
Decision evidence
public snapshot- The npm postinstall hook automatically runs both settings and agent-harness bootstrappers.
- The harness installer uses the current user's home directory without a user command or confirmation.
- It targets shared agent skill directories for both generic agents and Claude.
- Installation deletes existing Lanesmith-named skill directories, then copies package-provided skills into those agent control surfaces.
- The postinstall also refreshes global Lanesmith settings under the user's home directory.
- No source evidence of credential harvesting, arbitrary code evaluation, or direct network requests during installation.
- The harness cleanup is restricted to Lanesmith-named files and directories rather than unrelated agent content.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage ships non-JavaScript build or shell helper files.
share/settings/templates/github-actions/direct/release-direct.shFindings
Affected versions and remediation
This report applies to @keemgunn/lanesmith@1.4.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @keemgunn/lanesmith@1.4.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.