@splendidlabz/styles
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:@splendidlabz/utils | AI (phantom-deps): Same-org sibling dep in a monorepo; not directly imported in this CSS-focused package is expected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private/internal scoped CSS package; missing metadata is consistent across all versions, not a malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established scoped package family; missing description is cosmetic, not a risk indicator here. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.10.1 | 1 / 5 | |
| 4.9.0 | 1 / 5 | |
| 4.8.2 | 1 / 5 | |
| 4.8.1 | 1 / 5 | |
| 4.8.0 | 1 / 5 | |
| 4.7.1 | 1 / 5 | |
| 4.7.0 | 1 / 5 | |
| 4.6.8 | 1 / 5 | |
| 4.6.7 | 1 / 5 | |
| 4.6.6 | 1 / 5 | |
| 4.6.5 | 1 / 5 | |
| 4.6.4 | 1 / 5 | |
| 4.6.3 | 1 / 5 | |
| 4.6.2 | 1 / 5 | |
| 4.6.1 | 1 / 5 | |
| 4.6.0 | 1 / 5 | |
| 4.5.2 | 1 / 5 | |
| 4.5.1 | 1 / 5 | |
| 4.5.0 | 1 / 5 | |
| 4.4.1 | 1 / 5 | |
| 4.4.0 | 1 / 5 | |
| 4.3.2 | 1 / 5 | |
| 4.3.1 | 1 / 5 | |
| 4.3.0 | 1 / 5 | |
| 4.2.2 | 1 / 5 | |
| 4.2.1 | 1 / 5 | |
| 4.2.0 | 1 / 5 | |
| 4.1.0 | 1 / 5 | |
| 4.0.1 | 1 / 5 | |
| 4.0.0 | 1 / 5 |
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.