@delorenj/pjangler@1.5.18
Project subsystem bootstrapper CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiSource inspection found no npm install hook or concrete attack behavior. The scanner’s similarity labels are routing hints; the inspected code supports a clean verdict.
Decision evidence
public snapshot- package.json defines a prepublishOnly validation and build script, with no install-time hook.
- The flagged bundle locations define project skill search roots and fields owned by the project registry.
- Registry service setup is exposed as a separate npm script that creates and enables a user service.
- The flagged asset is a Python test suite that invokes the project hook script with test arguments.
- The prompt entrypoint reads a Hermes template configuration path from an environment setting or the user config directory.
- The registry client resolves a configured registry location and uses it for registry requests.
- The journal service listens on the loopback interface.
- One optional integration defaults off unless a project is eligible or explicitly enabled.
Source & flagged code
14 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.18.
See all versions of @delorenj/pjangler for other recorded verdicts.
- Review the evidence and your use of @delorenj/pjangler@1.5.18 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.