@oclif/plugin-help
Standard help 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash is used indirectly through oclif framework patterns; legitimate for this plugin. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Strip-ansi used indirectly in help formatting; stable pattern for oclif plugins. | ai | |
| phantom-deps | phantom-dep:@oclif/config | AI (phantom-deps): Core oclif dependency used indirectly through plugin system; expected for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/errors | AI (phantom-deps): Core oclif dependency used indirectly; stable pattern for oclif plugins. | ai | |
| dependencies | unvetted-dep:@oclif/cmd | AI (dependencies): @oclif/cmd is an npm alias for @oclif/[email protected], a core oclif package. This aliasing pattern is intentional and benign. | ai | |
| provenance | no-provenance | AI (provenance): Established oclif ecosystem package predating widespread provenance adoption; absence is expected and not a risk signal here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used intentionally to load user-configured custom help classes via oclif's plugin extension mechanism — a stable, documented pattern for this package. | ai | |
| phantom-deps | phantom-dep:string-width | AI (phantom-deps): string-width is a direct runtime dependency used by the help formatter; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:indent-string | AI (phantom-deps): indent-string is a direct runtime dependency used by the help formatter; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/command | AI (phantom-deps): Core oclif framework dependency; expected for oclif plugins; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:lodash.template | AI (phantom-deps): lodash.template is a direct runtime dependency used by the help formatter; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:wrap-ansi | AI (phantom-deps): wrap-ansi is a direct runtime dependency used by the help formatter; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a direct runtime dependency used by the help formatter; legitimate for this package. | ai | |
| phantom-deps | phantom-dep:widest-line | AI (phantom-deps): widest-line is a direct runtime dependency used by the help formatter; legitimate for this package. | ai |
Versions (showing 97 of 197)
| Version | Deps | Published |
|---|---|---|
| 5.1.18 | 1 / 13 | |
| 5.1.17 | 1 / 13 | |
| 5.1.16 | 1 / 13 | |
| 5.1.15 | 1 / 13 | |
| 5.1.14 | 1 / 13 | |
| 5.1.13 | 1 / 13 | |
| 5.1.12 | 1 / 13 | |
| 5.1.11 | 1 / 13 | |
| 5.1.10 | 1 / 13 | |
| 5.1.9 | 1 / 13 | |
| 5.1.8 | 1 / 13 | |
| 5.1.7 | 1 / 13 | |
| 5.1.6 | 1 / 13 | |
| 5.1.5 | 1 / 13 | |
| 5.1.4 | 1 / 13 | |
| 5.1.3 | 1 / 13 | |
| 5.1.2 | 1 / 13 | |
| 5.1.1 | 1 / 13 | |
| 5.1.0 | 1 / 14 | |
| 5.0.1 | 1 / 14 | |
| 5.0.0 | 1 / 14 | |
| 4.0.3 | 1 / 14 | |
| 4.0.2 | 1 / 14 | |
| 4.0.1 | 1 / 14 | |
| 4.0.0 | 1 / 14 | |
| 3.3.1 | 11 / 20 | |
| 3.3.0 | 1 / 14 | |
| 3.2.20 | 11 / 20 | |
| 3.2.19 | 11 / 20 | |
| 3.2.18 | 11 / 20 | |
| 3.2.17 | 10 / 20 | |
| 3.2.16 | 10 / 20 | |
| 3.2.15 | 10 / 20 | |
| 3.2.14 | 10 / 20 | |
| 3.2.13 | 10 / 20 | |
| 3.2.12 | 10 / 20 | |
| 3.2.11 | 10 / 20 | |
| 3.2.10 | 10 / 20 | |
| 3.2.9 | 10 / 20 | |
| 3.2.8 | 10 / 20 | |
| 3.2.7 | 10 / 20 | |
| 3.2.6 | 10 / 20 | |
| 3.2.5 | 10 / 20 | |
| 3.2.4 | 10 / 20 | |
| 3.2.3 | 10 / 20 | |
| 3.2.2 | 10 / 20 | |
| 3.2.1 | 10 / 20 | |
| 3.2.0 | 9 / 21 | |
| 3.1.0 | 9 / 21 | |
| 3.0.1 | 9 / 21 | |
| 3.0.0 | 9 / 20 | |
| 2.2.3 | 8 / 20 | |
| 2.2.2 | 8 / 21 | |
| 2.2.1 | 8 / 20 | |
| 2.2.0 | 8 / 20 | |
| 2.1.6 | 8 / 20 | |
| 2.1.4 | 8 / 20 | |
| 2.1.3 | 8 / 20 | |
| 2.1.2 | 8 / 20 | |
| 2.1.1 | 7 / 21 | |
| 2.1.0 | 7 / 22 | |
| 2.0.5 | 7 / 22 | |
| 2.0.4 | 7 / 22 | |
| 2.0.3 | 7 / 22 | |
| 2.0.2 | 7 / 22 | |
| 2.0.1 | 7 / 22 | |
| 2.0.0 | 7 / 22 | |
| 1.2.11 | 7 / 22 | |
| 1.2.10 | 7 / 22 | |
| 1.2.9 | 7 / 22 | |
| 1.2.8 | 7 / 22 | |
| 1.2.7 | 7 / 22 | |
| 1.2.6 | 7 / 22 | |
| 1.2.5 | 7 / 22 | |
| 1.2.4 | 7 / 22 | |
| 1.2.3 | 7 / 22 | |
| 1.2.2 | 7 / 22 | |
| 1.2.1 | 7 / 22 | |
| 1.2.0 | 7 / 22 | |
| 1.1.8 | 7 / 22 | |
| 1.1.7 | 7 / 22 | |
| 1.1.6 | 7 / 22 | |
| 1.1.5 | 7 / 22 | |
| 1.1.4 | 7 / 22 | |
| 1.1.3 | 7 / 22 | |
| 1.1.2 | 7 / 22 | |
| 1.1.1 | 7 / 22 | |
| 1.1.0 | 7 / 22 | |
| 1.0.5 | 7 / 22 | |
| 1.0.4 | 7 / 22 | |
| 1.0.3 | 7 / 22 | |
| 1.0.2 | 7 / 22 | |
| 1.0.1 | 7 / 22 | |
| 1.0.0 | 7 / 21 | |
| 0.7.4 | 7 / 21 | |
| 0.7.3 | 7 / 21 | |
| 0.7.2 | 7 / 21 |
v5.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage 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.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.