@delorenj/pjangler@1.5.13
Project subsystem bootstrapper CLI
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found no npm install lifecycle trigger or concrete malicious behavior. The flagged agent integration and service setup are explicit package operations, while the excluded-path payload is test code using local temporary fixtures.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook; prepublishOnly runs checks and a build.
- The flagged locations in the three bundles contain shared skill-root and registry-key constants, not agent configuration writes.
- Notebook skill and hook installation is exposed through an integration method, not an npm lifecycle hook.
- The registry service installer is a separate script that creates a user systemd unit when invoked.
- The flagged Python file is a test module that uses a temporary directory and local hook fixtures.
- The bundles include code for installing a first-party notebook skill and projecting hooks into Claude settings when the integration is invoked.
- The separate registry installer enables a user systemd service when run.
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.13.
See all versions of @delorenj/pjangler for other recorded verdicts.
- Review the evidence and your use of @delorenj/pjangler@1.5.13 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.