CLI for Primitive's decision graph — passive decision capture, conflict gate, and team presence
Allowed — no malicious behavior detected
13 low-signal patterns reviewed and cleared.
AI security review
scanned · by lpm-firewall-ai
Source inspection found no npm install lifecycle hook or concrete attack behavior. Scanner matches resolve to explicit CLI integration setup, guarded commit capture, and ordinary diff and YAML dependency code.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs a hook, integration, or setup command; the post-commit hook runs after a commit when capture is enabled.
Impact
No unauthorized account action, credential theft, destructive behavior, or remote code execution was identified.
Mechanism
Setup writes the selected integration files. The post-commit hook records commit metadata locally and launches this package’s flush command.
Decision evidence
public snapshot
Evidence for AI clean decision
package.json lists CLI commands but no install lifecycle hook; git hooks are installed through an explicit CLI command.
The Claude plugin is written by the skill-install path, and the command supports a dry run.
The post-commit hook checks that repository capture is active, reads commit metadata, records an event, and starts this package’s flush command.
The flagged account-action matches in the `diff` dependency implement text-diff array processing; they do not change authenticated accounts.
The inspected dependency files contain YAML parsing, composing, and stringifying code.
This dependency manifest lists clean, build:node, and test scripts and has no install lifecycle script.
Automated scan signals; the review checked them and cleared this version. Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.