@adyen/bento-design-tokens
Welcome to the Bento Design Tokens library!
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Both publishers are Adyen org accounts; transition appears to be an internal maintainer handoff. | ai |
Versions (showing 100 of 141)
| Version | Deps | Published |
|---|---|---|
| 1.104.0 | 0 / 8 | |
| 1.103.0 | 0 / 8 | |
| 1.102.0 | 0 / 8 | |
| 1.101.2 | 0 / 8 | |
| 1.101.1 | 0 / 8 | |
| 1.101.0 | 0 / 8 | |
| 1.100.1 | 0 / 8 | |
| 1.100.0 | 0 / 8 | |
| 1.99.0 | 0 / 8 | |
| 1.98.0 | 0 / 8 | |
| 1.97.0 | 0 / 8 | |
| 1.96.1 | 0 / 8 | |
| 1.96.0 | 0 / 8 | |
| 1.95.0 | 0 / 8 | |
| 1.94.0 | 0 / 8 | |
| 1.93.0 | 0 / 8 | |
| 1.92.2 | 0 / 8 | |
| 1.92.1 | 0 / 8 | |
| 1.92.0 | 0 / 8 | |
| 1.91.0 | 0 / 8 | |
| 1.90.0 | 0 / 8 | |
| 1.89.2 | 0 / 8 | |
| 1.89.1 | 0 / 8 | |
| 1.88.1 | 0 / 8 | |
| 1.88.0 | 0 / 8 | |
| 1.87.1 | 0 / 8 | |
| 1.87.0 | 0 / 8 | |
| 1.86.1 | 0 / 8 | |
| 1.86.0 | 0 / 8 | |
| 1.85.0 | 0 / 8 | |
| 1.84.2 | 0 / 8 | |
| 1.84.1 | 0 / 8 | |
| 1.84.0 | 0 / 8 | |
| 1.83.1 | 0 / 8 | |
| 1.83.0 | 0 / 8 | |
| 1.82.0 | 0 / 8 | |
| 1.81.1 | 0 / 8 | |
| 1.81.0 | 0 / 8 | |
| 1.80.0 | 0 / 8 | |
| 1.79.1 | 0 / 8 | |
| 1.79.0 | 0 / 8 | |
| 1.78.2 | 0 / 8 | |
| 1.78.1 | 0 / 8 | |
| 1.78.0 | 0 / 8 | |
| 1.77.1 | 0 / 8 | |
| 1.77.0 | 0 / 8 | |
| 1.76.2 | 0 / 8 | |
| 1.76.1 | 0 / 8 | |
| 1.76.0 | 0 / 8 | |
| 1.75.0 | 0 / 10 | |
| 1.74.0 | 0 / 10 | |
| 1.73.0 | 0 / 10 | |
| 1.72.0 | 0 / 10 | |
| 1.71.0 | 0 / 10 | |
| 1.70.0 | 0 / 8 | |
| 1.69.0 | 0 / 8 | |
| 1.68.2 | 0 / 8 | |
| 1.68.1 | 0 / 8 | |
| 1.68.0 | 0 / 8 | |
| 1.67.0 | 0 / 8 | |
| 1.66.0 | 0 / 8 | |
| 1.65.0 | 0 / 8 | |
| 1.64.1 | 0 / 8 | |
| 1.64.0 | 0 / 8 | |
| 1.63.2 | 0 / 8 | |
| 1.63.1 | 0 / 8 | |
| 1.63.0 | 0 / 8 | |
| 1.62.1 | 0 / 8 | |
| 1.61.0 | 0 / 8 | |
| 1.59.0 | 0 / 8 | |
| 1.58.1 | 0 / 8 | |
| 1.57.1 | 0 / 8 | |
| 1.57.0 | 0 / 8 | |
| 1.56.2 | 0 / 8 | |
| 1.56.0 | 0 / 8 | |
| 1.55.0 | 0 / 8 | |
| 1.54.2 | 0 / 8 | |
| 1.54.1 | 0 / 8 | |
| 1.53.0 | 0 / 8 | |
| 1.52.0 | 0 / 8 | |
| 1.51.0 | 0 / 8 | |
| 1.50.0 | 0 / 6 | |
| 1.49.0 | 0 / 5 | |
| 1.48.0 | 0 / 5 | |
| 1.47.1 | 0 / 5 | |
| 1.47.0 | 0 / 5 | |
| 1.46.0 | 0 / 5 | |
| 1.45.0 | 0 / 5 | |
| 1.44.0 | 0 / 5 | |
| 1.43.0 | 0 / 5 | |
| 1.42.0 | 0 / 5 | |
| 1.41.0 | 0 / 3 | |
| 1.40.0 | 0 / 3 | |
| 1.39.0 | 0 / 3 | |
| 1.38.1 | 0 / 3 | |
| 1.38.0 | 0 / 3 | |
| 1.37.0 | 0 / 3 | |
| 1.36.0 | 0 / 3 | |
| 1.35.1 | 0 / 3 | |
| 1.35.0 | 0 / 3 |
v1.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.