@fleettools/cli
FleetTools Global CLI - Fleet management and project bootstrapping
Supply chain provenance
Status for the latest visible version.
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 @fleettools/cli; Levenshtein match to 'joi' is coincidental, not a squatting attempt. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Monorepo workspace package bundled with bun build; deps inlined at build time, not imported directly. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Same as above — bun-bundled monorepo package. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Same as above — bun-bundled monorepo package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Same as above — bun-bundled monorepo package. | ai | |
| phantom-deps | phantom-dep:@fleettools/core | AI (phantom-deps): Same-org workspace dependency; bundled at build time. | ai | |
| phantom-deps | phantom-dep:@fleettools/shared | AI (phantom-deps): Same-org workspace dependency; bundled at build time. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 6 / 3 | |
| 0.2.5 | 6 / 3 | |
| 0.2.4 | 6 / 3 | |
| 0.2.3 | 6 / 3 | |
| 0.2.1 | 6 / 3 |
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.