verdaccio-okta-oauth@39.2.0
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no automatic lifecycle execution, and its potentially sensitive npm configuration change occurs only through its explicit login CLI for a configured non-public registry. Source inspection shows no secret harvesting, exfiltration endpoint, hidden payload, or persistence beyond that user-invoked authentication flow.
Decision evidence
public snapshot- The user-invoked CLI opens an OAuth endpoint and listens on localhost for its callback.
- The CLI writes an OAuth-returned token into npm configuration for the selected registry.
- The distributed CLI contains the same token-configuration behavior as the TypeScript source.
- The manifest declares a CLI executable at ./bin/index.js.
- The manifest has a bin entry but no install lifecycle scripts.
- The token is scoped to the configured registry and the default public npm registry is rejected.
- The plugin's network requests use the configured OAuth issuer for token and user-info flows; no fixed external collection endpoint is present.
Source & flagged code
5 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgThe distributed CLI contains the same token-configuration behavior as the TypeScript source.
dist/cli.jsView on unpkg · L31Findings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@39.2.0.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@39.2.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.