@tapi-dev/sdk@0.3.11
## Live Railway server diagnostics (operator MCP)
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe active CLI forwards cached service credentials to an unrestricted configured endpoint, warranting a warning under the credential-forwarding policy. No separate concrete attack evidence supports blocking publication.
Decision evidence
public snapshot- package.json has no automatic install lifecycle hooks.
- dist/auth.js reads existing Tapi credentials from its authentication cache.
- dist/cli.js activates workflow commands with the cached credential provider.
- dist/workflow-cli.js accepts a server from workspace configuration or --server and pairs it with the cached token.
- dist/dev-context.js selects the configured server without enforcing a destination allowlist.
- dist/client.js sends the token as bearer authentication to the selected endpoint; dist/runner-dev.js also forwards it during enrollment.
- The default API destination is package-aligned.
- The exposed behavior requires a user-invoked CLI command and a configured destination.
- No concrete covert recipient or malicious install behavior was established.
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.11.
See all versions of @tapi-dev/sdk for other recorded verdicts.
- Review the evidence and your use of @tapi-dev/sdk@0.3.11 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.