tnega@0.5.3
A minimal agent harness with spacetime-composable plugin lifecycles.
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no malicious behavior. The publish-only test hook, older self-dependency, configured model requests, and flagged tokenizer and browser modules do not establish an attack.
Decision evidence
public snapshot- package.json has a publish-only test hook and a runtime dependency on an older tnega release; that release also has only a publish-only test hook.
- The CLI is exposed as a command, and the reviewed runtime excerpts show session-event writes, error-stack handling, and loop detection.
- Model requests use a selected or configured route and send its key to that route’s base URL; no unrelated package-selected recipient was found.
- The flagged SQL and VBScript assets contain language-tokenizer code, and the other cited browser and dependency files are bundled application or protocol modules.
- The scanner’s install-time concern is not supported by the manifests: neither release declares a consumer install hook.
- The high-similarity asset matches are consistent with SQL and VBScript language support; the inspected code parses language tokens.
- The CLI’s authenticated requests follow configured model routes, while the inspected runtime excerpts show application behavior rather than an independent collection or persistence mechanism.
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.3.
See all versions of tnega for other recorded verdicts.
- Review the evidence and your use of tnega@0.5.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.