@confect/cli
Developer tooling for codegen and sync
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 package @confect/cli is unrelated to joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@effect/printer | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires on indirect/transitive usage pattern, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@effect/platform-node-shared | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires on indirect/transitive usage pattern, stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 8 / 14 | |
| 7.0.0 | 7 / 15 | |
| 6.0.0 | 7 / 15 | |
| 5.0.0 | 7 / 15 | |
| 4.0.0 | 7 / 15 | |
| 3.0.0 | 7 / 15 | |
| 2.0.0 | 7 / 15 | |
| 1.0.3 | 7 / 15 | |
| 1.0.2 | 7 / 15 | |
| 1.0.1 | 7 / 15 | |
| 1.0.0 | 8 / 15 |
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.