@oclif/errors
display friendly CLI errors and log to error log
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 | missing-githead | AI (provenance): Established oclif package with strong publisher track record; missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a process gap, not a security indicator, for this long-established oclif ecosystem package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): salesforce-releases is Salesforce's official release bot; oclif is a Salesforce project. This maintainer addition reflects a legitimate organizational consolidation, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Individual maintainers removed as part of Salesforce's consolidation of oclif under salesforce-releases bot. Consistent with known organizational transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with Salesforce organizational transition period for oclif packages. No malicious indicators in the version diff. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from oclif-bot to dickeyxxx (Jeff Dickey) is a legitimate transition — dickeyxxx is the named author of the package and the original oclif creator. This occurred in 2018 and is stable. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.3.6 | 5 / 18 | |
| 1.3.5 | 5 / 18 | |
| 1.3.4 | 5 / 18 | |
| 1.3.3 | 5 / 18 | |
| 1.3.2 | 5 / 18 | |
| 1.3.1 | 5 / 18 | |
| 1.3.0 | 5 / 18 | |
| 1.2.2 | 5 / 16 | |
| 1.2.1 | 5 / 16 | |
| 1.2.0 | 5 / 17 | |
| 1.1.2 | 5 / 17 | |
| 1.1.1 | 5 / 17 | |
| 1.1.0 | 5 / 17 | |
| 1.0.12 | 5 / 17 | |
| 1.0.11 | 5 / 17 | |
| 1.0.10 | 5 / 17 | |
| 1.0.9 | 5 / 17 | |
| 1.0.8 | 5 / 17 | |
| 1.0.7 | 5 / 17 | |
| 1.0.6 | 5 / 17 | |
| 1.0.5 | 5 / 17 | |
| 1.0.4 | 5 / 17 | |
| 1.0.3 | 5 / 17 | |
| 1.0.2 | 5 / 17 | |
| 1.0.1 | 5 / 16 | |
| 1.0.0 | 5 / 16 | |
| 0.2.2 | 5 / 16 | |
| 0.2.1 | 5 / 15 |
v1.3.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: amphro.
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 2021-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chadian.
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-11-12. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.3
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-06-29. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.2
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: chadian.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chadian.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chadian.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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 2018-08-17. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage 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 findingPackage 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-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2018-02-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage 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 2018-02-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.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 2018-02-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.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.