registry / atlas-project-harness / 0.1.0-beta.20
atlas-project-harness@0.1.0-beta.20
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource review found no install hook or concrete attack behavior. The network request is limited to the user-invoked report flow and sends the GitHub token to GitHub’s API.
Static reason
No blocking static signals were detected.
Trigger
A user invokes the CLI report command or a Pi extension command; the turn-end check follows completed tool activity in an initialized project.
Impact
No unconsented credential disclosure, destructive behavior, or automatic account action was established.
Mechanism
The extension checks project status and may run a local validation script. The report command obtains a GitHub token and sends it to the GitHub API for issue creation.
AI rationale
Source review found no install hook or concrete attack behavior. The network request is limited to the user-invoked report flow and sends the GitHub token to GitHub’s API.
Evidence
package.jsontests/test_shared_kernel.pyextensions/pi.tsbin/atlas.jsscripts/atlas_report.py
Network endpoints1
api.github.com/repos/{repo}/issues
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the CLI and Pi extension; its scripts are limited to tests and documentation, with no install lifecycle hook.
- The flagged test file contains ordinary profile parsing tests and fixtures.
- The extension registers an interactive command and runs checks only after completed tool activity in an initialized Atlas project.
- The report command obtains a GitHub token and uses it with the GitHub API only when reporting is invoked.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcebin/atlas.jsView file
1#!/usr/bin/env node
L2: const { spawnSync } = require('child_process');
L3: const path = require('path');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/atlas.jsView on unpkg · L1patches/workflow-skill-routing/apply-patches.pyView file
•path = patches/workflow-skill-routing/apply-patches.py
kind = build_helper
sizeBytes = 10653
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
patches/workflow-skill-routing/apply-patches.pyView on unpkgtests/test_shared_kernel.pyView file
Findings
2 High5 Medium5 Low
HighPayload In Excluded Dirtests/test_shared_kernel.py
HighSemantic Analysis Limitedextensions/pi.ts#virtual:normalized:round1
MediumDynamic Requirebin/atlas.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperpatches/workflow-skill-routing/apply-patches.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to atlas-project-harness@0.1.0-beta.20.
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.20 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.