verdaccio-okta-oauth@39.1.0
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package implements a user-invoked Verdaccio/Okta OAuth flow and has no automatic install-time execution. Its registry-scoped token setup is package-aligned and no concrete exfiltration, persistence, or payload behavior was found.
Decision evidence
public snapshot- The published manifest exposes a CLI but has no install lifecycle scripts.
- The source CLI, when explicitly run, writes an authentication token only for the selected registry and redirects the OAuth result.
- The built CLI matches the reviewed TypeScript source.
- No preinstall, install, or postinstall hook is present.
- No hard-coded remote endpoint, secret harvesting, payload download, or persistence was found.
- OAuth network requests use the configured issuer and registry as part of the package function.
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 built CLI matches the reviewed TypeScript source.
dist/cli.jsView on unpkg · L31Findings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@39.1.0.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@39.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.