tina4-nodejs@3.13.154
Tina4 for Node.js/TypeScript - native TypeScript conventions and shared Tina4 contracts
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner’s malicious labels. The highlighted behaviors resolve to build hooks, explicitly invoked setup helpers, gated MCP access, and ordinary framework and database functionality.
Decision evidence
public snapshot- The manifest’s `prepare` and `prepublishOnly` scripts run the build.
- AI context changes are made by setup helpers reached through the CLI’s explicit install command.
- The MCP settings helper writes a local server entry; remote MCP access requires explicit enablement and a valid token.
- AI provider keys and endpoints are configured for standard providers or caller-supplied settings; inspected database code uses configured database URLs and adapters.
- The MCP environment listing redacts values whose names indicate secrets, passwords, tokens, keys, or credentials.
- Inspected source describes project context indexing, API documentation, queue backends, routing, sessions, metrics, and database functionality; no malicious behavior was identified.
Source & flagged code
25 flaggedSource appears to send environment or credential material to an external endpoint.
packages/core/dist/index.jsView on unpkg · L18Findings
Affected versions and remediation
This report applies to tina4-nodejs@3.13.154.
See all versions of tina4-nodejs for other recorded verdicts.
- Review the evidence and your use of tina4-nodejs@3.13.154 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.