@tapi-dev/sdk@0.3.6
### Read dropdown choices without recording a click
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe active development path forwards an existing service credential to an unrestricted configurable destination, meeting the credential-forwarding warning rule. No separate concrete malicious behavior supports publication blocking.
Decision evidence
public snapshot- The auth module reads the existing Tapi ID token and refresh token from its credential cache.
- Studio development refreshes cached credentials and passes them to runner enrollment.
- The development server can be supplied through command options or inherited from workspace configuration.
- Server normalization removes trailing slashes without restricting the destination host.
- Runner enrollment sends the cached ID token as a bearer credential to the selected server.
- The CLI activates this behavior through the Studio development command.
- No registry-install lifecycle hook or runtime self-dependency appears in package.json.
- The default server is the Tapi backend; exposure requires a different configured destination.
- Inspected process launches support explicitly invoked development and workflow operations; no covert 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.6.
See all versions of @tapi-dev/sdk for other recorded verdicts.
- Review the evidence and your use of @tapi-dev/sdk@0.3.6 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.