verdaccio-okta-oauth@39.0.1
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no lifecycle hook, and the flagged CLI code is consistent with user-invoked registry OAuth setup. The source similarity hint is not proof of malicious behavior, and the inspected plugin code follows the configured Okta authorization flow.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and has no install lifecycle hook.
- The CLI derives the registry from its argument or npm configuration and rejects the default public npm registry.
- The CLI stores the OAuth-returned npm token for that selected registry; the distribution build matches the TypeScript source.
- The plugin starts an OAuth authorization flow against its configured Okta issuer.
Source & flagged code
8 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgThe CLI stores the OAuth-returned npm token for that selected registry; the distribution build matches the TypeScript source.
dist/cli.jsView on unpkg · L31The CLI derives the registry from its argument or npm configuration and rejects the default public npm registry.
Findings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@39.0.1.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@39.0.1 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.