atlas-project-harness@0.1.0-beta.37
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected entrypoints perform setup or checks through selected commands. The flagged test file contains fixtures, while the GitHub request belongs to the invoked report tool and sends supplied report fields to the GitHub API.
Decision evidence
public snapshot- The manifest points to the extension and CLI entrypoints and declares only test and documentation scripts; it has no install lifecycle hook.
- The extension registers workspace checks and setup as selectable Atlas commands.
- The CLI runs project setup from its init subcommand, using the current directory by default or a supplied target.
- The flagged test file contains parser fixtures, including a loopback URL, rather than an active network request.
- The report tool posts caller-supplied report fields to GitHub when invoked with a token; no covert credential collection or unrelated recipient was established.
Source & flagged code
6 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/atlas.jsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
bin/atlas.jsView on unpkgFindings
Affected versions and remediation
This report applies to atlas-project-harness@0.1.0-beta.37.
See all versions of atlas-project-harness for other recorded verdicts.
- Review the evidence and your use of atlas-project-harness@0.1.0-beta.37 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.