@oclif/command
oclif base command
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 org package; missing gitHead reflects a publish environment change, not a security concern. Stable false positive for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): oclif-bot removal is part of the same Salesforce org transition; not indicative of a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @oclif/config and @oclif/plugin-help are first-party oclif packages from the same org; natural dependencies for this base command package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are named Salesforce engineers and salesforce-releases account — consistent with Salesforce's stewardship of the oclif project. Legitimate org transition. | ai | |
| provenance | publisher-changed | AI (provenance): The dickeyxxx → oclif-bot transition occurred in Feb 2018 and represents a legitimate move to an org automation account. 100+ subsequent versions confirm this is the official publisher for the oclif org. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads the package's own package.json to check Node version — entirely benign and stable for this package. | ai | |
| typosquat | typosquat.levenshtein:commander | AI (typosquat): @oclif/command is a legitimate Salesforce/oclif framework package, not a typosquat of commander. The scoped namespace, age, and publisher track record confirm this is a false positive. | ai |
Versions (showing 6 of 106)
| Version | Deps | Published |
|---|---|---|
| 1.2.24 | 1 / 15 | |
| 1.2.23 | 1 / 15 | |
| 1.2.22 | 1 / 14 | |
| 1.2.21 | 1 / 14 | |
| 1.2.20 | 1 / 15 | |
| 1.2.19 | 1 / 17 |
v1.2.24
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.2.23
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.2.22
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.2.21
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.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.