nixamp@0.51.0
It really whips the terminal's ass. A Winamp-shaped audio player for your terminal.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe remote token forwarding is an active, browser-triggered behavior, and the destination can be an arbitrary registered HTTP or HTTPS origin. The feature has an apparent server-management purpose, but forwarding the existing account session token leaves conditional credential exposure, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The browser app obtains the signed-in nixamp.com bearer token and loads the account's registered server URLs.
- When making API requests to a remote server, the app sends that bearer token in an Authorization header.
- The app selects a registered server on page load; server URLs may be any HTTP or HTTPS origin.
- The token is used by the app's server-management interface, and the server list is associated with the signed-in account.
- The manifest defines a CLI entry point and no install lifecycle hook; the forwarding path is in the browser application.
Source & flagged code
7 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/speech.jsView on unpkg · L230Package source references weak cryptographic algorithms.
dist/catalogs.jsView on unpkg · L127Findings
Affected versions and remediation
This report applies to nixamp@0.51.0.
See all versions of nixamp for other recorded verdicts.
- Review the evidence and your use of nixamp@0.51.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.