tnega@0.4.23
A minimal agent harness with spacetime-composable plugin lifecycles.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no registry-install lifecycle hook, so its self-dependency does not create the specified automatic nested install chain. Reviewed agent-related reads and skill tooling do not establish unconsented control-surface mutation or remote code execution.
Decision evidence
public snapshot- package.json defines only a prepublishOnly test command; it has no preinstall, install, or postinstall hook.
- The runtime dependency on tnega@^0.1.1 is present, but no registry-install lifecycle trigger activates a nested release chain.
- The three runtime files read workspace AGENTS.md as approval constraints; the inspected code does not write agent configuration.
- Remote skill installation is exposed as a user-invoked tool that takes a source argument and processes skill content.
- The flagged browser bundle’s dynamic function construction is in a setImmediate compatibility shim; the VBScript asset begins with formula-parsing code.
Source & flagged code
17 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/tools.jsView on unpkg · L2025Findings
Affected versions and remediation
This report applies to tnega@0.4.23.
See all versions of tnega for other recorded verdicts.
- Review the evidence and your use of tnega@0.4.23 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.