@builder6/cli
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped CLI package @builder6/cli; Levenshtein match to 'joi' is coincidental, no impersonation. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): oclif CLI pattern; deps referenced via config/manifest, not direct imports. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): oclif plugin loaded via oclif.manifest config, not direct import. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-plugins | AI (phantom-deps): oclif plugin loaded via oclif.manifest config, not direct import. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 4 / 9 | |
| 3.2.13 | 4 / 9 | |
| 3.2.3 | 4 / 9 | |
| 3.2.1 | 4 / 9 | |
| 3.2.0 | 4 / 9 | |
| 3.1.2 | 4 / 9 | |
| 3.1.1 | 4 / 9 | |
| 3.1.0 | 4 / 9 |
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.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.3
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
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.