atlas-project-harness@0.2.0-beta.3
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 51m ago · by lpm-firewall-aiSource inspection found no package install lifecycle hook or concrete attack behavior. The flagged CLI setup and GitHub report paths are activated by explicit commands, and the test finding is ordinary parser-fixture code.
Decision evidence
public snapshot- package.json exposes the CLI and Pi extension without defining an install lifecycle hook.
- The Pi extension registers an explicit `/atlas` command; setup runs only when its `init` command is selected.
- The flagged test file contains parser fixtures, including a localhost URL, rather than an executable payload.
- The CLI runs the installer in response to the `init` command.
- The report tool obtains a GitHub credential and sends a report to GitHub only when the report command is invoked.
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.3.
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.3 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.