@baseline-ui/tokens
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
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.62.0 | 4 / 5 | |
| 0.61.0 | 4 / 5 | |
| 0.60.1 | 4 / 5 | |
| 0.60.0 | 4 / 5 | |
| 0.59.0 | 4 / 5 | |
| 0.58.0 | 4 / 5 | |
| 0.57.2 | 4 / 5 | |
| 0.57.1 | 4 / 5 | |
| 0.57.0 | 4 / 5 | |
| 0.56.0 | 4 / 6 | |
| 0.55.0 | 4 / 6 | |
| 0.54.2 | 4 / 6 | |
| 0.54.1 | 4 / 6 | |
| 0.54.0 | 4 / 6 | |
| 0.53.0 | 4 / 6 | |
| 0.52.0 | 4 / 6 | |
| 0.51.0 | 4 / 6 | |
| 0.50.0 | 4 / 6 | |
| 0.49.1 | 4 / 6 | |
| 0.49.0 | 4 / 6 | |
| 0.48.6 | 4 / 6 | |
| 0.48.5 | 4 / 6 | |
| 0.48.4 | 4 / 6 | |
| 0.48.3 | 4 / 6 | |
| 0.48.2 | 4 / 6 | |
| 0.48.1 | 4 / 6 | |
| 0.48.0 | 4 / 6 | |
| 0.47.0 | 4 / 6 | |
| 0.46.2 | 4 / 6 | |
| 0.46.1 | 4 / 6 | |
| 0.46.0 | 3 / 6 | |
| 0.45.8 | 3 / 6 | |
| 0.45.7 | 3 / 6 | |
| 0.45.6 | 3 / 6 | |
| 0.45.5 | 3 / 6 | |
| 0.45.4 | 3 / 6 | |
| 0.45.3 | 3 / 6 | |
| 0.45.2 | 3 / 6 | |
| 0.45.1 | 3 / 6 | |
| 0.45.0 | 3 / 6 | |
| 0.44.2 | 2 / 6 | |
| 0.44.1 | 1 / 6 | |
| 0.44.0 | 1 / 6 | |
| 0.43.0 | 1 / 6 |
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.