@oclif/core
base library for oclif CLIs
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Salesforce-maintained package with 454 versions and strong track record; periodic dormancy between releases is normal for stable CLI framework libraries. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Top-level fetch in CLI config initialization is a legitimate pattern; no evidence of exfiltration. | ai | |
| phantom-deps | phantom-dep:@types/cli-progress | AI (phantom-deps): TypeScript type definitions loaded by convention; expected for @types/* packages in CLI frameworks. | ai | |
| dependencies | unvetted-dep:@types/cli-progress | AI (dependencies): Type definitions for established cli-progress package; legitimate dev-time dependency. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 76 new files expected for major version rewrite of oclif framework; legitimate TypeScript source expansion. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): minimatch@^9.0.3 is an established, widely-trusted glob pattern library; legitimate addition for CLI framework. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal without new maintainers is normal in mature projects; no takeover signal. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is a best-practice gap, not a security issue for this established package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): The new Function() call is a documented CJS/ESM interop workaround for dynamic import() in TypeScript-compiled code. Input is a resolved module path, not arbitrary user input. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly declared as a runtime dependency in package.json. This is a false positive; tslib is a standard TypeScript runtime helper used by this package. | ai | |
| dependencies | unvetted-dep:ejs | AI (dependencies): ejs is a standard, legitimate templating library; appropriate dependency for CLI framework. | ai | |
| dependencies | unvetted-dep:ansi-escapes | AI (dependencies): ansi-escapes is a legitimate, widely-used terminal utility; stable dependency for this CLI framework. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @oclif package; Levenshtein match to 'cors' is coincidental, not typosquatting. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require of ts-node is a standard pattern in CLI frameworks for optional TypeScript support; constrained to known module, not arbitrary code execution. | ai |
Versions (showing 68 of 168)
| Version | Deps | Published |
|---|---|---|
| 3.25.0 | 28 / 46 | |
| 3.24.0 | 28 / 46 | |
| 3.23.1 | 28 / 46 | |
| 3.23.0 | 28 / 46 | |
| 3.22.0 | 28 / 46 | |
| 3.21.2 | 27 / 46 | |
| 3.21.1 | 27 / 46 | |
| 3.21.0 | 27 / 46 | |
| 3.20.0 | 27 / 46 | |
| 3.19.7 | 27 / 46 | |
| 3.19.6 | 27 / 46 | |
| 3.19.5 | 27 / 46 | |
| 3.19.4 | 27 / 46 | |
| 3.19.3 | 27 / 46 | |
| 3.19.2 | 27 / 46 | |
| 3.19.1 | 27 / 46 | |
| 3.19.0 | 27 / 46 | |
| 3.18.2 | 27 / 46 | |
| 3.18.1 | 27 / 46 | |
| 3.18.0 | 26 / 47 | |
| 3.17.0 | 27 / 47 | |
| 3.16.0 | 27 / 47 | |
| 3.15.1 | 27 / 47 | |
| 3.15.0 | 27 / 47 | |
| 3.14.1 | 27 / 47 | |
| 3.14.0 | 27 / 47 | |
| 3.13.2 | 27 / 47 | |
| 3.13.1 | 27 / 47 | |
| 3.13.0 | 27 / 47 | |
| 3.12.1 | 27 / 47 | |
| 3.12.0 | 27 / 47 | |
| 3.11.0 | 26 / 46 | |
| 3.10.8 | 26 / 46 | |
| 3.10.7 | 26 / 46 | |
| 3.10.6 | 26 / 46 | |
| 3.10.5 | 26 / 46 | |
| 3.10.4 | 26 / 46 | |
| 3.10.3 | 26 / 46 | |
| 3.10.2 | 26 / 46 | |
| 3.10.1 | 26 / 46 | |
| 3.10.0 | 26 / 46 | |
| 3.9.2 | 25 / 45 | |
| 3.9.1 | 25 / 45 | |
| 3.9.0 | 25 / 45 | |
| 3.8.0 | 25 / 45 | |
| 3.7.1 | 25 / 45 | |
| 3.7.0 | 25 / 45 | |
| 3.6.0 | 25 / 45 | |
| 3.5.0 | 25 / 44 | |
| 3.4.0 | 25 / 44 | |
| 3.3.3 | 25 / 44 | |
| 3.3.2 | 25 / 44 | |
| 3.3.1 | 25 / 44 | |
| 3.3.0 | 25 / 44 | |
| 3.2.1 | 25 / 44 | |
| 3.2.0 | 25 / 44 | |
| 3.1.0 | 25 / 44 | |
| 3.0.9 | 25 / 44 | |
| 3.0.8 | 25 / 45 | |
| 3.0.7 | 25 / 45 | |
| 3.0.6 | 25 / 45 | |
| 3.0.5 | 25 / 45 | |
| 3.0.4 | 25 / 46 | |
| 3.0.3 | 25 / 46 | |
| 3.0.2 | 25 / 46 | |
| 3.0.1 | 25 / 46 | |
| 3.0.0 | 25 / 46 | |
| 1.0.10 | 17 / 36 |
v3.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package 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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.