tina4-nodejs@3.13.152
Tina4 for Node.js/TypeScript - native TypeScript conventions and shared Tina4 contracts
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection supports ordinary build, framework, and explicitly invoked setup behavior. The flagged scanner labels are not substantiated by the inspected source excerpts as a concrete attack.
Decision evidence
public snapshot- The manifest exposes framework and CLI entrypoints; its prepare and prepublishOnly scripts run the build.
- AI context installation is reached through a CLI command that offers a selection menu or installs all only when the user passes --all; the AI tool list names its target configuration files.
- The MCP helper writes a project .claude/settings.json entry for a localhost server when called; the inspected code does not establish an automatic install-time configuration change.
- The inspected AI client and distribution code select named providers and use TINA4_AI_KEY for configured remote providers; the browser client attaches its stored token only when authentication is enabled and its URL passes the same-origin or configured API-origin check.
- The reviewed distribution and source paths show framework, database, routing, session, queue, and development-admin components; no concrete credential theft or payload execution was established in the inspected excerpts.
Source & flagged code
26 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.152.
See all versions of tina4-nodejs for other recorded verdicts.
- Review the evidence and your use of tina4-nodejs@3.13.152 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.