registry / @delorenj/pjangler / 1.5.16
@delorenj/pjangler@1.5.16
Project subsystem bootstrapper CLI
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or confirmed attack behavior. The scanner's agent-location hints resolve to skill-root data, while the API key use is part of the Plane ticket client.
Static reason
No blocking static signals were detected.
Trigger
The CLI or MCP entrypoint is invoked; registry service installation requires the explicit registry:install command.
Impact
No package-controlled harmful impact was established.
Mechanism
No malicious behavior was confirmed. The Plane client sends a workspace API key to its Plane API, and the indicated skill-root locations do not show agent configuration writes.
AI rationale
Source inspection found no install lifecycle hook or confirmed attack behavior. The scanner's agent-location hints resolve to skill-root data, while the API key use is part of the Plane ticket client.
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes CLI entrypoints; registry setup is an explicit registry:install command, and prepublishOnly runs checks and a build rather than an install hook.
- The three indicated bundled locations list shared skill directories followed by registry-owned project fields; they do not show writes to agent configuration.
- The registry installer writes a user systemd service and checks its health on localhost when explicitly invoked.
- The flagged Python file is test code that sets up temporary settings and a temporary state directory for its test helper.
- The Plane client reads a workspace API key from Plane-specific environment or local fleet settings and sends it as an X-API-Key to the Plane API, whose default base is plane.delo.sh.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
7 flagged · loading sourcedist/index.jsView file
•path = dist/index.js
kind = trigger_reachable_excluded_payload
sizeBytes = 911727
triggerReachableSource = dist/index.js
excludedPayload = .mise/scripts/versioning.sh
Critical
Trigger Reachable Excluded Directory Payload
A 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 unpkg121// src/project/registryClient.ts
L122: import { spawnSync } from "node:child_process";
L123: import { homedir as homedir2 } from "node:os";
High
•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
dist/index.js:
CREDENTIAL_KEY = /(?:^|[_-])(?:password|passwd|api[_-]?key|access[_-]?token|refresh[_-]?token|client[_-]?secret|private[_-]?key|credential|authorization)(?:$|[_-])/iu;
`no Plane API key for workspace "${workspace}": set ${planeApiKeyNames(workspace).join(" or ")}, or add one to ${ctx.env.HERMES_FLEET_ENV?.trim() || join12(ctx.home, ".hermes", "fl...
`Plane returned ${response.status} for ${path}` + (credentials ? ` \u2014 the API key was rejected; check ${planeApiKeyNames(client.workspace).join(" / ")}` : response.status === 4...
import { chmodSync as chmodSync2, closeSync, copyFileSync as copyFileSync2, existsSync as ex
Findings
1 Critical4 High5 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/index.js
HighChild Processdist/index.js
HighSame File Env Network Executionscripts/install-project-registry.mjs
HighCredential Redirect Persistencedist/index.js
HighPayload In Excluded Dirdist/assets/project-notebook-skill/tests/test_project_hooks.py
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdist/assets/project-notebook-skill/tests/test_project_hooks.py
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Low
Affected versions and remediation
This report applies to @delorenj/pjangler@1.5.16.
See all versions of @delorenj/pjangler for other recorded verdicts.
- Review the evidence and your use of @delorenj/pjangler@1.5.16 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.