@ant-design/x-markdown
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only in benchmark dev scripts, not in published runtime code. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 5 / 20 | |
| 2.7.0 | 5 / 20 | |
| 2.6.0 | 5 / 20 | |
| 2.5.0 | 5 / 20 | |
| 2.4.0 | 5 / 20 | |
| 2.3.0 | 5 / 20 | |
| 2.2.2 | 5 / 22 | |
| 2.2.1 | 5 / 22 | |
| 2.2.0 | 5 / 22 | |
| 2.1.3 | 5 / 10 | |
| 2.1.2 | 5 / 10 | |
| 2.1.1 | 5 / 10 | |
| 2.1.0 | 5 / 10 |
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.