tracist@0.0.39
Upload and continuously stream local AI coding transcripts to Tracist
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo lifecycle hook or stealth install-time behavior exists, so a publish block is not warranted. The documented transcript uploader nevertheless installs a persistent daemon whose default behavior accepts remote queued prompts with privileged agent settings.
Decision evidence
public snapshot- scripts/capture-resume-multiturn.js opens an authenticated machine WebSocket and accepts queue_session control.
- Queued prompts are passed to local agent CLIs with approval/sandbox bypass flags.
- bin/tracist.js install explicitly creates a persistent user daemon that runs the queue-enabled streamer.
- The default streamer enables control; --upload-only is the opt-out mode.
- package.json has no preinstall/install/postinstall hooks.
- Persistence requires the explicit tracist install command.
- README.md accurately describes transcript upload and the user-service daemon.
- Outbound transcript events are routed through tools/secret-redaction.js.
Source & flagged code
7 flagged · loading sourceSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
bin/tracist.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to tracist@0.0.39.
See all versions of tracist for other recorded verdicts.
- Review the evidence and your use of tracist@0.0.39 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.