@promptctl/cc-candybar@1.161.2
Statusline renderer for Claude Code — a JSON5-configurable DSL with daemon-cached data sources, byte-clean palette-aware composition, and OSC8 click verbs.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package has no install-time lifecycle hook, and the flagged command execution and network behavior align with its CLI and statusline functionality. The scanner's invisible-character hint corresponds to JavaScript identifier handling; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest points to the CLI bundle; its prepublishOnly script runs validation and build steps.
- The CLI shim imports the bundle, and its command runner handles process output as part of runtime behavior.
- The bundled runtime includes a command runner and output formatting consistent with the package's CLI features.
- The flagged invisible characters appear in JavaScript identifier continuation logic; searches found no bidi override controls.
- The three inspected platform-specific native dependency manifests contain no lifecycle scripts.
- The bundle can run configured commands and makes a request to the project's pricing data host; the inspected source did not establish unauthorized collection or transfer.
Source & flagged code
8 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/index.mjsView on unpkg · L9A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.mjsView on unpkg · L480Findings
Affected versions and remediation
This report applies to @promptctl/cc-candybar@1.161.2.
See all versions of @promptctl/cc-candybar for other recorded verdicts.
- Review the evidence and your use of @promptctl/cc-candybar@1.161.2 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.