@styleframe/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:defu | AI (phantom-deps): Utility library used in config/build; declared in dependencies and referenced in build setup. | ai | |
| phantom-deps | phantom-dep:culori | AI (phantom-deps): Color utility library; declared in dependencies and used in theme logic. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.7.0 | 3 / 9 | |
| 3.6.0 | 3 / 9 | |
| 3.5.1 | 3 / 9 | |
| 3.5.0 | 3 / 9 | |
| 3.4.0 | 3 / 9 | |
| 3.3.0 | 3 / 9 | |
| 3.2.0 | 3 / 9 | |
| 3.1.0 | 3 / 9 | |
| 3.0.0 | 3 / 9 | |
| 2.5.0 | 2 / 9 | |
| 2.4.0 | 2 / 9 | |
| 2.3.0 | 2 / 9 | |
| 2.2.0 | 2 / 9 | |
| 2.1.0 | 2 / 9 | |
| 2.0.3 | 2 / 9 | |
| 2.0.2 | 2 / 9 | |
| 2.0.1 | 2 / 9 | |
| 2.0.0 | 2 / 9 | |
| 1.0.3 | 2 / 9 | |
| 1.0.2 | 2 / 9 |
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.