tnega@0.5.1
A minimal agent harness with spacetime-composable plugin lifecycles.
AI Security Review
scanned 21d ago · by lpm-firewall-aiInspected source does not establish unconsented install mutation, credential disclosure, or another concrete attack. The scanner hints resolve to package-aligned runtime and frontend code, while the self-dependency has no install lifecycle trigger.
Decision evidence
public snapshot- package.json lists a prepublishOnly test command and a tnega self-dependency, with no preinstall, install, or postinstall hook.
- The targeted agent code reads workspace AGENTS.md as constraints and treats a missing file as empty; these locations do not mutate agent settings.
- The runtime hints resolve to error-stack handling and JSONL event logging in project-loop, not account actions.
- The flagged frontend assets contain SQL and VBScript tokenizers and preview bundles; ExcelJS constructs a string Function in a setImmediate polyfill.
- The execution sandbox rejects HTTP destinations that resolve to private or reserved addresses.
- The plugin-development description says host-process plugin code needs approval and that failed imports or mounts are rolled back.
- The package includes agent execution and plugin-development capabilities, including a string Function call in a bundled browser polyfill.
Source & flagged code
19 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/tools.jsView on unpkg · L2031Findings
Affected versions and remediation
This report applies to tnega@0.5.1.
See all versions of tnega for other recorded verdicts.
- Review the evidence and your use of tnega@0.5.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.