nixamp@0.71.0
⚠ Under reviewIt really whips the terminal's ass. A Winamp-shaped audio player for your terminal.
AI Security Review
scanned 13h ago · by lpm-firewall-aiThe flagged browser code’s token forwarding is consistent with managing servers registered to the signed-in user, and the inspected sources do not establish exfiltration to a fixed package-controlled receiver. Several selected registry dependencies are unavailable for source review, so their runtime behavior remains unresolved and requires manual review.
Decision evidence
public snapshot- The flagged browser bundle reads the signed-in nixamp token and uses it for servers in the account’s server list; the package source describes those as the user’s own machines.
- The user can register a server URL through an explicit CLI command, and the server list is scoped to the signed-in account.
- The package imports several selected registry dependencies whose source was unavailable in the supplied snapshot, so their runtime behavior remains unresolved.
- The inspected browser code does not establish that the token is sent to a fixed package-controlled receiver; it uses account-listed server URLs.
- The package manifest has no install lifecycle hook, and the CLI entry imports the application’s main module.
Source & flagged code
20 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/speech.jsView on unpkg · L230Findings
Affected versions and remediation
This report applies to nixamp@0.71.0.
See all versions of nixamp for other recorded verdicts.
- Review the evidence and your use of nixamp@0.71.0 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.