registry / agency-lang / 0.19.1
agency-lang@0.19.1
The Agency language
AI Security Review
scanned 24d ago · by lpm-firewall-aiInspected source shows package features with explicit user-facing activation and safeguards, and the manifest lists no install lifecycle hook. The scanner hints map to ordinary runtime capabilities and do not establish malicious behavior.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
No malicious trigger was identified; the reviewed operations are invoked through package features such as optimization, OAuth, or subprocess execution.
Impact
No confirmed malicious effect or attack surface was established from the inspected source.
Mechanism
The inspected source shows hash-checked workspace writes, bounded IPC resource use, HTTPS checks for OAuth endpoints, and user-authored optimizer loading.
AI rationale
Inspected source shows package features with explicit user-facing activation and safeguards, and the manifest lists no install lifecycle hook. The scanner hints map to ordinary runtime capabilities and do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and runtime entrypoints; its listed scripts are development commands, with no install lifecycle hook shown.
- Workspace writeback is an explicit operation that checks source hashes and writes only changed files.
- The IPC runtime clamps user-supplied resource limits and uses subprocesses for runtime work.
- OAuth endpoints are required to use HTTPS, except for localhost development.
- Untrusted compiled output has a sandbox option that disables code generation from strings.
- Optimizer modules are user-authored, compiled, and loaded on request.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
7 flaggeddist/lib/optimize/workspace.jsView file
6/** Mint a fresh cache-partition token. */
L7: fork() {
L8: this.counter += 1;
High
Child Process
Package source references child process execution.
dist/lib/optimize/workspace.jsView on unpkg · L6dist/lib/runtime/ipc.jsView file
388env: { ...process.env, AGENCY_IPC: "1" },
L389: execArgv: [`--max-old-space-size=${memoryMb}`],
L390: ...(args.cwd ? { cwd: args.cwd } : {}),
High
dist/lib/optimize/optimizerModule.jsView file
32// eslint-disable-next-line no-restricted-syntax -- CLI-layer loading of a user artifact; the bundle path is only known at runtime
L33: const mod = await import(pathToFileURL(out).href);
L34: const factory = mod.default;
Findings
5 High4 Medium5 Low
HighChild Processdist/lib/optimize/workspace.js
HighShelldist/lib/runtime/ipc.js
HighSame File Env Network Executiondist/lib/stdlib/oauth.js
HighSemantic Analysis Limiteddist/lib/cli/commands.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/lib/cli/commands.js
MediumDynamic Requiredist/lib/optimize/optimizerModule.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/lib/cli/schedule/backends/launchd.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to agency-lang@0.19.1.
See all versions of agency-lang for other recorded verdicts.
- Review the evidence and your use of agency-lang@0.19.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.