@tapi-dev/sdk@0.3.8
## Application runs own their cleanup
AI Security Review
scanned 22d ago · by lpm-firewall-aiStatic source inspection establishes conditional forwarding of an existing service credential to an unrestricted configured endpoint. This warrants a warning under the credential-forwarding policy, without evidence sufficient to classify the package as malware.
Decision evidence
public snapshot- package.json has no automatic npm installation hooks or runtime self-dependency.
- dist/auth.js reads an existing Tapi ID token from the credential cache.
- dist/cli.js loads cached credentials when the user invokes runner dev.
- dist/runner-dev.js sends the ID token as bearer authentication to the selected server.
- dist/dev-context.js accepts the configured server without a destination allowlist; dist/runner-dev.js accepts --server.
- dist/workflow-cli.js also obtains the server from workspace configuration.
- The default destination is the Tapi service, and activation requires a user command.
- No hidden credential recipient or concrete malware intent was established.
Source & flagged code
14 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.8.
See all versions of @tapi-dev/sdk for other recorded verdicts.
- Review the evidence and your use of @tapi-dev/sdk@0.3.8 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.