@goobit/ai@0.0.2
AI Git Collaboration Governance & Smart Skill Hub for Heterogeneous AI Agents
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s automatic postinstall performs unconsented writes to project-level AI agent control files. This meets the policy for blocking lifecycle-triggered mutation of a foreign AI control surface.
Decision evidence
public snapshot- The package runs a postinstall script automatically.
- The hook targets the external project in INIT_CWD and calls setupGovernance without an affirmative consent check.
- Setup writes AGENTS.md and harness instruction files into the target project, including Claude, Cursor, and Gemini configuration locations.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs a postinstall script automatically.
package.jsonView on unpkg · L14Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
bin/harness-bridge.jsView on unpkg · L4Manifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/harness-bridge.jsView on unpkgPackage source references weak cryptographic algorithms.
bin/harness-bridge.jsView on unpkg · L19The hook targets the external project in INIT_CWD and calls setupGovernance without an affirmative consent check.
bin/postinstall.jsView on unpkg · L11Findings
Affected versions and remediation
This report applies to @goobit/ai@0.0.2.
See all versions of @goobit/ai for other recorded verdicts.
- Avoid installing @goobit/ai@0.0.2. 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.