@stryke/type-checks
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from stormie-bot to GitHub Actions as part of a CI/CD automation migration. SLSA provenance attestation confirms legitimate pipeline publishing. This is stable for this package going forward. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Low-value signals (off-topic README, no keywords) are cosmetic issues in an established 409-day-old package with 39 approved dependents. Not a security concern. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 0.6.17 | 1 / 1 | |
| 0.6.16 | 1 / 1 | |
| 0.6.15 | 1 / 1 | |
| 0.6.14 | 1 / 1 | |
| 0.6.13 | 1 / 1 | |
| 0.6.12 | 1 / 1 | |
| 0.6.11 | 1 / 1 | |
| 0.6.10 | 1 / 1 | |
| 0.6.9 | 1 / 1 | |
| 0.6.8 | 1 / 1 | |
| 0.6.7 | 1 / 1 | |
| 0.6.6 | 0 / 1 | |
| 0.6.5 | 0 / 1 | |
| 0.6.4 | 0 / 1 | |
| 0.6.3 | 0 / 1 | |
| 0.6.2 | 0 / 1 | |
| 0.6.1 | 0 / 1 | |
| 0.6.0 | 0 / 1 | |
| 0.5.41 | 0 / 1 | |
| 0.5.40 | 0 / 1 | |
| 0.5.39 | 0 / 1 | |
| 0.5.38 | 0 / 1 | |
| 0.5.37 | 0 / 1 | |
| 0.5.36 | 0 / 1 | |
| 0.5.35 | 0 / 1 | |
| 0.5.34 | 0 / 1 | |
| 0.5.33 | 0 / 1 | |
| 0.5.32 | 0 / 1 | |
| 0.5.31 | 0 / 1 | |
| 0.5.30 | 0 / 1 | |
| 0.5.29 | 0 / 1 | |
| 0.5.28 | 0 / 1 | |
| 0.5.27 | 0 / 1 | |
| 0.5.26 | 0 / 1 | |
| 0.5.25 | 0 / 1 | |
| 0.5.23 | 0 / 1 | |
| 0.5.22 | 0 / 1 | |
| 0.5.21 | 0 / 1 | |
| 0.5.20 | 0 / 1 | |
| 0.5.19 | 0 / 1 | |
| 0.5.18 | 0 / 1 | |
| 0.5.17 | 0 / 1 | |
| 0.5.16 | 0 / 1 | |
| 0.5.15 | 0 / 1 | |
| 0.5.14 | 0 / 1 | |
| 0.5.13 | 0 / 1 | |
| 0.5.12 | 0 / 1 | |
| 0.5.11 | 0 / 1 | |
| 0.5.10 | 0 / 1 | |
| 0.5.9 | 0 / 1 | |
| 0.5.8 | 0 / 1 |
v0.6.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.10
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (stormie-bot) than the most recent previously approved version (GitHub Actions) on 2026-05-25, but stormie-bot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.35
2 findingsThis version was published by a different npm account than previous versions on 2026-03-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.