@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, 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 |
|---|---|---|---|---|
| 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 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 2.101.1 | 14 / 16 | |
| 2.101.0 | 14 / 16 | |
| 2.100.0 | 14 / 16 | |
| 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 | |
| 2.93.0 | 14 / 16 | |
| 2.92.2 | 14 / 16 | |
| 2.92.1 | 14 / 16 | |
| 2.92.0 | 14 / 16 | |
| 2.91.0 | 14 / 16 | |
| 2.90.13 | 14 / 16 | |
| 2.90.12 | 14 / 16 | |
| 2.90.11 | 14 / 16 | |
| 2.90.10 | 14 / 16 | |
| 2.90.9 | 14 / 16 | |
| 2.90.8 | 14 / 16 | |
| 2.90.7 | 14 / 16 | |
| 2.90.6 | 14 / 16 | |
| 2.90.5 | 14 / 16 | |
| 2.90.4 | 14 / 16 | |
| 2.90.3 | 14 / 16 | |
| 2.90.2 | 14 / 16 | |
| 2.90.1 | 14 / 15 | |
| 2.90.0 | 14 / 15 | |
| 2.89.1 | 14 / 15 | |
| 2.89.0 | 14 / 15 | |
| 2.88.3 | 14 / 15 | |
| 2.88.2 | 14 / 15 | |
| 2.88.1 | 14 / 15 | |
| 2.88.0 | 14 / 15 | |
| 2.1.1 | 9 / 12 | |
| 2.1.0 | 9 / 12 | |
| 2.0.8 | 9 / 12 | |
| 2.0.7 | 9 / 12 | |
| 2.0.6 | 9 / 12 | |
| 2.0.5 | 9 / 12 | |
| 2.0.4 | 9 / 12 | |
| 2.0.3 | 9 / 12 | |
| 2.0.2 | 9 / 12 | |
| 2.0.1 | 9 / 12 | |
| 2.0.0 | 9 / 12 |
v2.101.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (semi-bot) than the most recent previously approved version (point.halo) on 2025-12-18, but semi-bot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.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.88.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.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.