command-line-usage
Generates command-line usage information
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 | new-deps-added | AI (publish-pattern): New deps (array-back, table-layout, feature-detect-es6) are all by the same trusted maintainer (75lb) and consistent with the package's formatting/layout purpose. Not a suspicious injection. | ai | |
| dependencies | unvetted-dep:feature-detect-es6 | AI (dependencies): feature-detect-es6 is a small, purpose-specific utility used for ES5 transpilation fallback logic; consistent with this package's documented ES5 build workflow. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects a major version rewrite (v1→v3) with new features, added es5/ transpiled output directory, and new dependencies — not injected payloads. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in bin/cli.js is intentional CLI behavior — loads a user-specified file to generate usage output. Not a security risk for this package. | ai | |
| dependencies | unvetted-dep:typical | AI (dependencies): typical is a utility package by the same author (75lb/Lloyd Brookes); part of the same ecosystem and expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is absent but this is common (~88% of packages); trusted publisher with long track record mitigates this concern. | ai | |
| dependencies | unvetted-dep:array-back | AI (dependencies): array-back is a utility package by the same author (75lb/Lloyd Brookes); part of the same ecosystem and expected dependency. | ai | |
| dependencies | unvetted-dep:table-layout | AI (dependencies): table-layout is a utility package by the same author (75lb/Lloyd Brookes); part of the same ecosystem and expected dependency. | ai | |
| dependencies | unvetted-dep:chalk-template | AI (dependencies): chalk-template is a well-known chalk ecosystem package; its use here for terminal color templating is expected and legitimate. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 7.0.4 | 4 / 5 | |
| 7.0.3 | 4 / 5 | |
| 7.0.2 | 4 / 5 | |
| 7.0.1 | 4 / 5 | |
| 7.0.0 | 4 / 2 | |
| 6.1.3 | 4 / 2 | |
| 6.1.2 | 4 / 2 | |
| 6.1.1 | 4 / 4 | |
| 6.1.0 | 4 / 4 | |
| 6.0.2 | 4 / 4 | |
| 6.0.1 | 4 / 4 | |
| 6.0.0 | 4 / 4 | |
| 5.0.5 | 4 / 2 | |
| 5.0.4 | 4 / 2 | |
| 5.0.3 | 4 / 2 | |
| 5.0.2 | 4 / 2 | |
| 5.0.1 | 4 / 2 | |
| 5.0.0 | 4 / 2 | |
| 4.1.0 | 4 / 2 | |
| 4.0.2 | 4 / 2 | |
| 4.0.1 | 4 / 2 | |
| 4.0.0 | 4 / 2 | |
| 3.0.8 | 5 / 4 | |
| 3.0.7 | 5 / 4 | |
| 3.0.6 | 5 / 4 | |
| 3.0.5 | 5 / 4 | |
| 3.0.4 | 5 / 4 | |
| 3.0.3 | 5 / 3 | |
| 3.0.2 | 5 / 3 | |
| 3.0.1 | 5 / 3 | |
| 3.0.0 | 5 / 3 | |
| 2.0.5 | 6 / 3 | |
| 2.0.4 | 5 / 3 | |
| 2.0.3 | 6 / 3 | |
| 2.0.2 | 6 / 2 | |
| 2.0.1 | 6 / 2 | |
| 2.0.0 | 6 / 2 | |
| 1.2.1 | 6 / 2 | |
| 1.2.0 | 6 / 2 | |
| 1.1.2 | 6 / 2 | |
| 1.1.1 | 6 / 2 | |
| 1.1.0 | 6 / 2 | |
| 1.0.0 | 5 / 2 |
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v5.0.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.
v5.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.
v5.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.
v5.0.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.
v5.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.
v5.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.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
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.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.