@spark-web/theme
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@spark-web/utils | AI (phantom-deps): Same org scope (@spark-web); likely re-exported or used indirectly in build output rather than directly imported. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 5.13.3 | 7 / 4 | |
| 5.13.2 | 7 / 4 | |
| 5.13.1 | 7 / 4 | |
| 5.13.0 | 7 / 4 | |
| 5.12.9 | 7 / 4 | |
| 5.12.8 | 7 / 4 | |
| 5.12.7 | 7 / 4 | |
| 5.12.6 | 7 / 4 | |
| 5.12.5 | 7 / 4 | |
| 5.12.4 | 7 / 4 | |
| 5.12.3 | 7 / 4 | |
| 5.12.2 | 7 / 4 | |
| 5.12.1 | 7 / 4 | |
| 5.11.1 | 7 / 4 | |
| 5.11.0 | 7 / 4 | |
| 5.10.6 | 7 / 4 | |
| 5.10.5 | 7 / 4 | |
| 5.10.4 | 7 / 4 | |
| 5.10.3 | 7 / 4 | |
| 5.10.2 | 7 / 4 | |
| 5.10.1 | 7 / 4 | |
| 5.10.0 | 7 / 4 | |
| 5.9.3 | 7 / 4 | |
| 5.9.2 | 7 / 4 | |
| 5.9.1 | 7 / 4 | |
| 5.9.0 | 7 / 4 | |
| 5.8.0 | 7 / 4 | |
| 5.7.2 | 7 / 4 | |
| 5.7.1 | 7 / 4 | |
| 5.7.0 | 7 / 4 | |
| 5.6.1 | 7 / 4 | |
| 5.6.0 | 7 / 4 | |
| 5.5.1 | 7 / 4 | |
| 5.5.0 | 7 / 4 | |
| 5.4.0 | 7 / 4 | |
| 5.3.1 | 7 / 4 | |
| 5.3.0 | 7 / 4 | |
| 5.2.0 | 7 / 4 | |
| 5.1.0 | 7 / 4 | |
| 5.0.0 | 7 / 4 |
v5.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brighte-release-bot) than the most recent previously approved version (brighte) on 2025-03-16, but brighte-release-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.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brighte) than the most recent previously approved version (brighte-release-bot) on 2025-03-15, but brighte 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.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.