@douyinfe/semi-foundation
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established ByteDance Semi Design monorepo package; semi-bot is a legitimate CI publisher; missing metadata is a known pattern for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Large ByteDance design system; no provenance is consistent across all 600+ prior versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.99.3 | 14 / 16 | |
| 2.99.2 | 14 / 16 | |
| 2.99.1 | 14 / 16 | |
| 2.99.0 | 14 / 16 | |
| 2.98.0 | 14 / 16 | |
| 2.97.0 | 14 / 16 | |
| 2.96.1 | 14 / 16 | |
| 2.96.0 | 14 / 16 | |
| 2.95.1 | 14 / 16 | |
| 2.95.0 | 14 / 16 | |
| 2.94.1 | 14 / 16 | |
| 2.94.0 | 14 / 16 |
v2.99.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.97.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.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.
v2.94.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.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.