verdaccio-okta-oauth@40.1.0
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found a reachable callback that executes a command containing request input and redirects a JWT to a request-supplied destination. The CLI is user-invoked, so this is an unresolved conditional risk rather than evidence of install-time malware.
Decision evidence
public snapshot- The published CLI entrypoint starts a local HTTP callback listener when invoked.
- The callback inserts a request parameter into an npm configuration command executed by a shell, creating a command injection risk for requests that reach the listener.
- The callback redirects to a request-supplied URI and includes a JWT token in the redirect query.
- The CLI is explicitly exposed as a command-line tool, and its npm token configuration and OAuth callback behavior appear intended for registry authentication.
Source & flagged code
6 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
src/cli.tsView on unpkgFindings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@40.1.0.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@40.1.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.