@tapi-dev/sdk@0.3.7
### Read dropdown choices without recording a click
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource confirms forwarding of an existing service token to an unrestricted operator-configured destination. The explicit development command and absence of concrete covert attack behavior warrant a warning rather than publication blocking.
Decision evidence
public snapshot- The authentication module reads an existing Tapi ID token from its credential cache and returns it when fresh.
- The CLI loads cached Tapi credentials when the user invokes runner dev.
- Runner development accepts an unrestricted --server argument, and development context uses it as the API destination.
- Runner enrollment sends the cached ID token as a Bearer credential to that destination.
- package.json has no automatic installation lifecycle hook.
- The credential transfer requires an explicit development command and a suitable source workspace.
- The default destination is the Tapi API; no hidden unrelated recipient or 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.7.
See all versions of @tapi-dev/sdk for other recorded verdicts.
- Review the evidence and your use of @tapi-dev/sdk@0.3.7 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.