@stryke/url
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 legitimate CI/CD migration for the storm-software/stryke monorepo, corroborated by SLSA provenance attestation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Low-score cosmetic signals (off-topic README content, no keywords) with no security relevance for this established URL utility package. | ai | |
| source-diff | obfuscated-file:dist/storm-url-t7pdfQNU.cjs | AI (source-diff): Minified bundle output from tsdown build tool; code is readable JS logic using known deps (ufo, superjson, jsonc-parser). Not obfuscation — standard minification for this package. | ai | |
| source-diff | obfuscated-file:dist/storm-url-DQn2usO1.mjs | AI (source-diff): Minified ESM bundle output from tsdown build tool; same readable logic as CJS counterpart. Standard minification, not obfuscation. | ai |
Versions (showing 82 of 82)
| Version | Deps | Published |
|---|---|---|
| 0.4.35 | 4 / 2 | |
| 0.4.34 | 4 / 2 | |
| 0.4.33 | 4 / 2 | |
| 0.4.32 | 4 / 2 | |
| 0.4.31 | 4 / 2 | |
| 0.4.30 | 4 / 2 | |
| 0.4.29 | 4 / 2 | |
| 0.4.28 | 4 / 2 | |
| 0.4.27 | 4 / 2 | |
| 0.4.26 | 4 / 2 | |
| 0.4.25 | 4 / 2 | |
| 0.4.24 | 4 / 2 | |
| 0.4.23 | 4 / 2 | |
| 0.4.22 | 4 / 2 | |
| 0.4.21 | 1 / 2 | |
| 0.4.20 | 1 / 2 | |
| 0.4.19 | 1 / 2 | |
| 0.4.18 | 1 / 2 | |
| 0.4.17 | 1 / 2 | |
| 0.4.16 | 1 / 2 | |
| 0.4.15 | 1 / 2 | |
| 0.4.14 | 1 / 2 | |
| 0.4.13 | 1 / 2 | |
| 0.4.12 | 1 / 2 | |
| 0.4.11 | 1 / 2 | |
| 0.4.10 | 1 / 2 | |
| 0.4.9 | 1 / 2 | |
| 0.4.8 | 1 / 2 | |
| 0.4.7 | 1 / 2 | |
| 0.4.6 | 1 / 2 | |
| 0.4.3 | 1 / 2 | |
| 0.4.2 | 1 / 2 | |
| 0.4.1 | 1 / 2 | |
| 0.4.0 | 1 / 2 | |
| 0.3.39 | 1 / 2 | |
| 0.3.38 | 1 / 2 | |
| 0.3.37 | 1 / 2 | |
| 0.3.36 | 1 / 2 | |
| 0.3.34 | 1 / 2 | |
| 0.3.33 | 1 / 2 | |
| 0.3.32 | 1 / 2 | |
| 0.3.31 | 1 / 2 | |
| 0.3.30 | 1 / 2 | |
| 0.3.29 | 1 / 2 | |
| 0.3.28 | 1 / 2 | |
| 0.3.27 | 1 / 2 | |
| 0.3.26 | 1 / 2 | |
| 0.3.25 | 1 / 2 | |
| 0.3.24 | 1 / 2 | |
| 0.3.23 | 1 / 2 | |
| 0.3.22 | 1 / 2 | |
| 0.3.21 | 1 / 2 | |
| 0.3.20 | 1 / 2 | |
| 0.3.19 | 1 / 2 | |
| 0.3.18 | 1 / 2 | |
| 0.3.17 | 1 / 2 | |
| 0.3.16 | 1 / 2 | |
| 0.3.15 | 1 / 2 | |
| 0.3.14 | 1 / 2 | |
| 0.3.13 | 1 / 2 | |
| 0.3.12 | 1 / 2 | |
| 0.3.11 | 1 / 2 | |
| 0.3.4 | 4 / 1 | |
| 0.3.3 | 4 / 1 | |
| 0.3.2 | 4 / 1 | |
| 0.3.1 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.13 | 4 / 1 | |
| 0.2.12 | 4 / 1 | |
| 0.2.11 | 4 / 1 | |
| 0.2.10 | 4 / 1 | |
| 0.2.9 | 4 / 1 | |
| 0.2.8 | 4 / 1 | |
| 0.2.7 | 4 / 1 | |
| 0.2.6 | 4 / 1 | |
| 0.2.5 | 4 / 1 | |
| 0.2.4 | 4 / 1 | |
| 0.2.3 | 4 / 1 | |
| 0.2.2 | 4 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.1 | 4 / 1 |
v0.4.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.28
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.4.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.10
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.3.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.14
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.12
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.11
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.