@tapi-dev/sdk@0.3.9
## Application runs own their cleanup
AI Security Review
scanned 22d ago · by lpm-firewall-aiStatic source inspection establishes conditional credential forwarding to an unrestricted configured destination, warranting a warning. No concrete malicious behavior or automatic install attack was identified.
Decision evidence
public snapshot- dist/auth.js reads an existing Tapi ID token from its credential cache.
- dist/cli.js supplies cached Firebase credentials to user-invoked workflow commands.
- dist/workflow-cli.js combines cached credentials with a configurable server; dist/dev-context.js applies no destination allowlist.
- dist/client.js sends the token as bearer authorization to the selected server.
- Studio development also forwards cached credentials through runner enrollment to the configured server.
- package.json contains no automatic install lifecycle hooks.
- Credential forwarding requires a user-invoked command and a configured alternative destination.
- The default server is used consistently by Tapi features; no hidden unrelated recipient was identified.
- Inspected process execution supports workflow and development commands.
Source & flagged code
13 flagged · loading sourcePackage source references child process execution.
dist/workflow-cli.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @tapi-dev/sdk@0.3.9.
See all versions of @tapi-dev/sdk for other recorded verdicts.
- Review the evidence and your use of @tapi-dev/sdk@0.3.9 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.