@delorenj/pjangler@1.5.14
Project subsystem bootstrapper CLI
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no install-time attack behavior. The scanner-flagged locations correspond to registry metadata, explicit service setup, and a test fixture reference.
Decision evidence
public snapshot- package.json defines no preinstall, install, or postinstall hook; prepublishOnly runs build and checks.
- The flagged locations in the three bundles list fields owned by a project registry, rather than writing agent configuration.
- The registry installer is a separate script that creates a user systemd service when explicitly run.
- The flagged Python file is a test that references project-notebook hook fixtures.
Source & flagged code
8 flagged · loading sourceA package entrypoint or install-reachable source explicitly loads and activates an executable-looking payload from a test, fixture, or hidden path.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @delorenj/pjangler@1.5.14.
See all versions of @delorenj/pjangler for other recorded verdicts.
- Review the evidence and your use of @delorenj/pjangler@1.5.14 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.