nopt
Option parsing for Node, supporting types, shorthands, etc. Used by npm.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): nopt is an official npm org package; missing gitHead reflects a publish environment change, not a security concern. Stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions as part of npm CLI team's standard automated publishing pipeline. SLSA provenance attestation confirms integrity. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): New maintainers are the npm CLI team at GitHub (gar, npm-cli-ops, etc.). Package is officially owned by GitHub Inc./npm org. SLSA provenance confirms legitimate CI/CD publishing. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known npm CLI team members at GitHub. Legitimate organizational ownership transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous maintainers removed as part of npm CLI team taking ownership. Consistent with GitHub/npm organizational transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by major version bump (5→9) reflects npm team modernization effort, not account takeover. SLSA provenance confirms legitimate publish. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): nopt is a completely different category of package from 'got'; the 2-edit Levenshtein distance is coincidental and not indicative of squatting. | ai | |
| provenance | no-provenance | AI (provenance): nopt is a legacy package predating Sigstore provenance; absence is expected and not a risk signal for this well-known, trusted package. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): nopt is a well-established npm option-parsing library predating 'nuxt'; the name similarity is purely coincidental and not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): nopt is a well-established npm option-parsing library predating 'next'; the name similarity is purely coincidental and not a typosquat. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 1 / 2 | |
| 9.0.0 | 1 / 3 | |
| 8.1.0 | 1 / 3 | |
| 8.0.0 | 1 / 3 | |
| 7.2.1 | 1 / 3 | |
| 7.2.0 | 1 / 3 | |
| 7.1.0 | 1 / 3 | |
| 7.0.0 | 1 / 3 | |
| 6.0.0 | 1 / 3 | |
| 5.0.0 | 1 / 1 | |
| 4.0.3 | 2 / 1 | |
| 4.0.2 | 2 / 1 | |
| 4.0.1 | 2 / 1 | |
| 4.0.0 | 2 / 1 | |
| 3.0.6 | 1 / 1 | |
| 3.0.5 | 1 / 1 | |
| 3.0.4 | 1 / 1 | |
| 3.0.3 | 1 / 1 | |
| 3.0.2 | 1 / 1 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 1 / 1 | |
| 2.2.1 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.2 | 1 / 0 | |
| 2.1.1 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.0.10 | 1 / 0 | |
| 1.0.9 | 1 / 0 | |
| 1.0.8 | 1 / 0 | |
| 1.0.7 | 1 / 0 | |
| 1.0.6 | 1 / 0 | |
| 1.0.5 | 1 / 0 | |
| 1.0.4 | 1 / 0 | |
| 1.0.3 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v10.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-01-21. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-09-04. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-15. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-20. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-08. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-12. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-12. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-09-10. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.