antd-token-previewer
Ant Design token previewer
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Ant Design ecosystem package with clean publisher history; lack of provenance is common and not a security concern here. | ai | |
| phantom-deps | phantom-dep:@ant-design/colors | AI (phantom-deps): @ant-design/colors is a legitimate Ant Design package; phantom dep finding is a minor packaging issue, not a security risk. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 11 / 26 | |
| 2.0.8 | 12 / 27 | |
| 2.0.5 | 12 / 27 | |
| 2.0.4 | 12 / 27 | |
| 2.0.3 | 12 / 27 | |
| 2.0.2 | 12 / 27 | |
| 2.0.1 | 12 / 27 | |
| 2.0.0 | 12 / 26 | |
| 1.1.0 | 11 / 25 | |
| 1.0.5 | 10 / 25 | |
| 1.0.4 | 10 / 25 | |
| 1.0.3 | 10 / 25 | |
| 1.0.2 | 10 / 25 | |
| 1.0.1 | 10 / 25 | |
| 1.0.0 | 10 / 25 |
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.