tracist@0.0.55
Upload and continuously stream local AI coding transcripts to Tracist
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo covert install-time behavior or evidence of malicious intent was found, and the core transcript-upload function is disclosed. However, the persistent remote control channel exposes broad file and agent-control capabilities beyond simple upload.
Decision evidence
public snapshot- scripts/capture-resume-multiturn.js accepts server filesystem list/read requests.
- Server-provided saves can overwrite existing files under an arbitrary supplied root.
- Persistent queue dispatch forwards server messages into local agent sessions.
- bin/tracist.js install creates a user daemon and auto-updates its private runtime.
- README.md accurately describes transcript upload and explicit install.
- package.json has only prepare; no preinstall/install/postinstall hook.
- Daemon installation requires explicit `tracist install`.
- Transcript uploads target the declared Tracist service and use token redaction.
Source & flagged code
7 flagged · loading sourceA manifest entrypoint or package-local install chain reaches persistence behavior.
bin/tracist.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to tracist@0.0.55.
See all versions of tracist for other recorded verdicts.
- Review the evidence and your use of tracist@0.0.55 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.