@stryke/convert
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, a standard CI/CD migration. SLSA provenance attestation confirms legitimate automated publishing pipeline for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Low-value signals (off-topic README, no keywords) have no security implications for this established utility package with 24 approved dependents. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 0.7.15 | 2 / 2 | |
| 0.7.14 | 2 / 2 | |
| 0.7.13 | 2 / 2 | |
| 0.7.12 | 2 / 2 | |
| 0.7.11 | 2 / 2 | |
| 0.7.10 | 2 / 2 | |
| 0.7.9 | 2 / 2 | |
| 0.7.8 | 2 / 2 | |
| 0.7.7 | 2 / 2 | |
| 0.7.6 | 2 / 2 | |
| 0.7.5 | 2 / 2 | |
| 0.7.4 | 0 / 2 | |
| 0.7.3 | 0 / 2 | |
| 0.7.2 | 0 / 2 | |
| 0.7.1 | 0 / 2 | |
| 0.7.0 | 0 / 2 | |
| 0.6.58 | 0 / 2 | |
| 0.6.57 | 0 / 2 | |
| 0.6.56 | 0 / 2 | |
| 0.6.55 | 0 / 2 | |
| 0.6.54 | 0 / 2 | |
| 0.6.53 | 0 / 2 | |
| 0.6.52 | 0 / 2 | |
| 0.6.51 | 0 / 2 | |
| 0.6.50 | 0 / 2 | |
| 0.6.49 | 0 / 2 | |
| 0.6.46 | 0 / 2 | |
| 0.6.45 | 0 / 2 | |
| 0.6.44 | 0 / 2 | |
| 0.6.43 | 0 / 2 | |
| 0.6.42 | 0 / 2 | |
| 0.6.41 | 0 / 2 | |
| 0.6.40 | 0 / 2 | |
| 0.6.38 | 0 / 2 | |
| 0.6.37 | 0 / 2 | |
| 0.6.36 | 0 / 2 | |
| 0.6.35 | 0 / 2 | |
| 0.6.34 | 0 / 2 | |
| 0.6.33 | 0 / 2 | |
| 0.6.32 | 0 / 2 | |
| 0.6.31 | 0 / 2 | |
| 0.6.30 | 0 / 2 | |
| 0.6.29 | 0 / 2 | |
| 0.6.28 | 0 / 2 | |
| 0.6.27 | 0 / 2 | |
| 0.6.26 | 0 / 2 | |
| 0.6.25 | 0 / 2 | |
| 0.6.24 | 0 / 2 | |
| 0.6.23 | 0 / 2 | |
| 0.6.22 | 0 / 2 | |
| 0.6.21 | 0 / 2 |
v0.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.8
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.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.6.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.53
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. 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.6.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.