atlas-project-harness@0.2.0-beta.1
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected CLI, extension, installer, and test behavior is user-invoked or test-scoped. The scanner's similarity and payload hints did not establish malicious behavior in the inspected source.
Decision evidence
public snapshot- The manifest defines no install lifecycle hook; its scripts are test and documentation commands.
- The Pi extension registers Atlas as a user command; checks and setup run through explicit commands or agent events.
- The CLI routes init to the package installer, which checks project state before updating.
- The flagged test helper dynamically loads local package modules for parser tests.
- The package includes a network-backed reporting command, but it is reached through the explicit report command.
- The installer writes Atlas project assets when explicitly run; no automatic install trigger is declared.
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 unpkgPackage source references dynamic require/import behavior.
Findings
Affected versions and remediation
This report applies to atlas-project-harness@0.2.0-beta.1.
See all versions of atlas-project-harness for other recorded verdicts.
- Review the evidence and your use of atlas-project-harness@0.2.0-beta.1 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.