@coti-io/coti-sdk-typescript
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI is expected for a maturing project; SLSA attestation confirms legitimate CI publish. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation and no code changes confirm this is a legitimate re-publish, not a takeover. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 1 / 11 | |
| 1.0.8 | 1 / 11 | |
| 1.0.7 | 1 / 11 | |
| 1.0.6 | 1 / 11 | |
| 1.0.4 | 1 / 6 | |
| 1.0.3 | 1 / 6 | |
| 1.0.2 | 1 / 6 | |
| 1.0.1 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.