registry / @agimon-ai/po-config / 0.0.0-alpha.93
@agimon-ai/po-config@0.0.0-alpha.93
Typed configuration loading, validation, and host services for composing Po sessions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no install lifecycle hooks, and the flagged dependency bridge reads and merges configuration rather than sending data. The inspected settings writes require a request and scope check, and no automatic hostile behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation, import, or explicit configuration API calls.
Impact
No hostile impact identified.
Mechanism
The inspected entry point wires configuration modules; the flagged bridge reads and merges config files, while settings writes are request-driven and scope-checked.
AI rationale
The package has no install lifecycle hooks, and the flagged dependency bridge reads and merges configuration rather than sending data. The inspected settings writes require a request and scope check, and no automatic hostile behavior was identified.
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 defines build and development scripts but no install lifecycle scripts.
- The main entry point loads configuration and support modules; no automatic attack behavior was identified in the inspected entry code.
- The flagged dependency bridge reads global and repository configuration files and merges their contents.
- The settings API writes configuration only after receiving a scoped request body and checking that the requested scope matches its context.
Evidence against
- Static scanner hints flagged filesystem, environment, network and dependency-bridge behavior, but the inspected code uses these for configuration and settings functions.
- The package exposes file-writing APIs, but the inspected settings handler requires an incoming request before writing.
Behavioral surface
CryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/config-ch_DJeTs.cjsView file
8package = @agimon-ai/po-config; repositoryIdentity = po; dependency = yaml
L8: node_fs = require_rolldown_runtime.__toESM(node_fs, 1);
L9: let yaml = require("yaml");
L10: //#region src/services/config/sync.ts
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/config-ch_DJeTs.cjsView on unpkg · L828/** @deprecated Node-only sync shim; use readPoConfig. Removed in M2. */
function loadPoConfig(repoRoot, homeDirectory = _agimon_ai_po_core_platform.nodeHost.homeDirectory(), environment = process.env) {
const globalPath = require_core.globalPoConfigPath(homeDirectory, environment);
const repositoryPath = require_core.repositoryConfigFor(repoRoot, homeDirectory, environment);
return require_core.mergeConfigLayers(require_co
Low
Suspicious Dependency Evidence
The flagged dependency bridge reads global and repository configuration files and merges their contents.
dist/config-ch_DJeTs.cjsView on unpkg · L28package.jsonView file
Findings
1 High3 Medium8 Low
HighCopied Package Dependency Bridgedist/config-ch_DJeTs.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.cjs
LowSuspicious Dependency Evidencedist/config-ch_DJeTs.cjs
LowAi Review Evidencedist/settingsApi-DQrXSdCR.cjs
Affected versions and remediation
This report applies to @agimon-ai/po-config@0.0.0-alpha.93.
See all versions of @agimon-ai/po-config for other recorded verdicts.
- Review the evidence and your use of @agimon-ai/po-config@0.0.0-alpha.93 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.