@oclif/plugin-not-found
"did you mean" for oclif
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dickeyxxx → oclif-bot is the well-known legitimate transition when oclif moved to automated bot publishing in 2018. | ai | |
| phantom-deps | phantom-dep:@oclif/command | AI (phantom-deps): @oclif/command is a peer/host dependency for oclif plugins — it is provided by the consuming CLI framework, not imported directly. This is the standard oclif plugin pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (rodesp, mdonnalley) are known oclif/Salesforce contributors; maintainer additions are routine for this actively maintained Salesforce-owned package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer delisting is consistent with Salesforce's organizational practices; no evidence of takeover. | ai | |
| dependencies | unvetted-dep:@oclif/color | AI (dependencies): @oclif/color is a first-party Salesforce/oclif dependency; its use in this oclif plugin is expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce's established publisher track record makes provenance absence acceptable for this version. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @inquirer/confirm is from an established ecosystem and aligns with the plugin's CLI purpose; legitimate addition. | ai | |
| dependencies | unvetted-dep:fast-levenshtein | AI (dependencies): fast-levenshtein is a well-known string-distance library appropriate for a 'did you mean' plugin; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: established oclif plugin with 184 prior versions; inflated semver reflects ecosystem convention, not spam. | ai |
Versions (showing 90 of 190)
| Version | Deps | Published |
|---|---|---|
| 3.0.12 | 3 / 23 | |
| 3.0.11 | 3 / 23 | |
| 3.0.10 | 3 / 23 | |
| 3.0.9 | 3 / 23 | |
| 3.0.8 | 3 / 23 | |
| 3.0.7 | 3 / 23 | |
| 3.0.6 | 3 / 23 | |
| 3.0.5 | 3 / 23 | |
| 3.0.4 | 3 / 23 | |
| 3.0.3 | 3 / 23 | |
| 3.0.2 | 3 / 23 | |
| 3.0.1 | 3 / 23 | |
| 2.4.3 | 3 / 17 | |
| 2.4.2 | 3 / 17 | |
| 2.4.1 | 3 / 17 | |
| 2.4.0 | 3 / 17 | |
| 2.3.38 | 3 / 17 | |
| 2.3.37 | 3 / 17 | |
| 2.3.36 | 3 / 17 | |
| 2.3.35 | 3 / 17 | |
| 2.3.34 | 3 / 17 | |
| 2.3.33 | 3 / 17 | |
| 2.3.32 | 3 / 17 | |
| 2.3.31 | 3 / 17 | |
| 2.3.30 | 3 / 17 | |
| 2.3.29 | 3 / 17 | |
| 2.3.28 | 3 / 17 | |
| 2.3.27 | 3 / 17 | |
| 2.3.26 | 3 / 17 | |
| 2.3.25 | 3 / 17 | |
| 2.3.24 | 3 / 17 | |
| 2.3.23 | 4 / 19 | |
| 2.3.22 | 4 / 19 | |
| 2.3.21 | 4 / 19 | |
| 2.3.20 | 4 / 19 | |
| 2.3.19 | 4 / 19 | |
| 2.3.18 | 4 / 19 | |
| 2.3.17 | 4 / 19 | |
| 2.3.16 | 4 / 19 | |
| 2.3.15 | 4 / 19 | |
| 2.3.14 | 4 / 19 | |
| 2.3.13 | 4 / 19 | |
| 2.3.12 | 4 / 19 | |
| 2.3.11 | 4 / 19 | |
| 2.3.10 | 4 / 19 | |
| 2.3.9 | 4 / 19 | |
| 2.3.8 | 4 / 19 | |
| 2.3.7 | 4 / 19 | |
| 2.3.6 | 4 / 19 | |
| 2.3.5 | 4 / 19 | |
| 2.3.4 | 4 / 19 | |
| 2.3.3 | 4 / 19 | |
| 2.3.2 | 4 / 19 | |
| 2.3.1 | 4 / 19 | |
| 2.3.0 | 4 / 19 | |
| 2.2.4 | 5 / 19 | |
| 2.2.3 | 5 / 19 | |
| 2.2.2 | 5 / 18 | |
| 2.2.1 | 5 / 18 | |
| 2.2.0 | 5 / 17 | |
| 2.1.4 | 5 / 19 | |
| 2.1.3 | 5 / 19 | |
| 2.1.2 | 5 / 19 | |
| 2.1.1 | 5 / 19 | |
| 2.1.0 | 5 / 19 | |
| 2.0.0 | 5 / 19 | |
| 1.2.6 | 5 / 19 | |
| 1.2.5 | 5 / 19 | |
| 1.2.4 | 5 / 19 | |
| 1.2.3 | 5 / 18 | |
| 1.2.2 | 5 / 18 | |
| 1.2.1 | 5 / 18 | |
| 1.2.0 | 5 / 19 | |
| 1.1.4 | 5 / 19 | |
| 1.1.3 | 5 / 19 | |
| 1.1.2 | 5 / 19 | |
| 1.1.1 | 5 / 19 | |
| 1.1.0 | 4 / 17 | |
| 1.0.9 | 3 / 16 | |
| 1.0.8 | 3 / 16 | |
| 1.0.7 | 3 / 16 | |
| 1.0.6 | 3 / 16 | |
| 1.0.5 | 3 / 16 | |
| 1.0.4 | 3 / 16 | |
| 1.0.3 | 3 / 16 | |
| 1.0.2 | 3 / 16 | |
| 1.0.1 | 3 / 16 | |
| 1.0.0 | 3 / 15 | |
| 0.1.21 | 3 / 15 | |
| 0.1.20 | 3 / 15 |
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.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.
v2.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.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.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.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.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
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.2.5
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.2.4
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.2.3
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.2.2
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.2.1
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.2.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.
v1.1.4
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.1.3
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.1.2
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.1.1
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.1.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.
v1.0.9
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.8
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.7
2 findingsThis version was published by a different npm account than previous versions on 2018-04-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
2 findingsThis version was published by a different npm account than previous versions on 2018-04-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
2 findingsThis version was published by a different npm account than previous versions on 2018-03-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
2 findingsThis version was published by a different npm account than previous versions on 2018-03-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version was published by a different npm account than previous versions on 2018-02-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-02-15. This could indicate a legitimate maintainer transition or an account compromise.
[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.