@douyinfe/semi-illustrations
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Official ByteDance Semi Design package (DouyinFE/semi-design, 37.7k dl/wk); semi-bot is its release bot, not spam. | ai |
Versions (showing 51 of 260)
| Version | Deps | Published |
|---|---|---|
| 2.101.1 | 0 / 10 | |
| 2.101.0 | 0 / 10 | |
| 2.100.0 | 0 / 10 | |
| 2.99.3 | 0 / 10 | |
| 2.99.2 | 0 / 10 | |
| 2.99.1 | 0 / 10 | |
| 2.99.0 | 0 / 10 | |
| 2.98.0 | 0 / 10 | |
| 2.97.0 | 0 / 10 | |
| 2.96.1 | 0 / 10 | |
| 2.96.0 | 0 / 10 | |
| 2.95.1 | 0 / 10 | |
| 2.95.0 | 0 / 10 | |
| 2.94.1 | 0 / 10 | |
| 2.94.0 | 0 / 10 | |
| 2.90.2 | 0 / 10 | |
| 2.89.0 | 0 / 10 | |
| 2.88.3 | 0 / 10 | |
| 2.88.2 | 0 / 10 | |
| 2.88.1 | 0 / 10 | |
| 2.88.0 | 0 / 10 | |
| 2.87.1 | 0 / 10 | |
| 2.87.0 | 0 / 10 | |
| 2.86.0 | 0 / 10 | |
| 2.85.0 | 0 / 10 | |
| 2.84.0 | 0 / 10 | |
| 2.83.0 | 0 / 10 | |
| 2.82.1 | 0 / 10 | |
| 2.82.0 | 0 / 10 | |
| 2.81.0 | 0 / 10 | |
| 2.80.0 | 0 / 10 | |
| 2.79.0 | 0 / 10 | |
| 2.78.0 | 0 / 10 | |
| 2.77.1 | 0 / 10 | |
| 2.77.0 | 0 / 10 | |
| 2.76.1 | 0 / 10 | |
| 2.76.0 | 0 / 10 | |
| 2.75.0 | 0 / 10 | |
| 2.74.0 | 0 / 10 | |
| 2.73.0 | 0 / 10 | |
| 2.72.3 | 0 / 10 | |
| 2.72.2 | 0 / 10 | |
| 2.72.1 | 0 / 10 | |
| 2.72.0 | 0 / 10 | |
| 2.71.3 | 0 / 10 | |
| 2.71.2 | 0 / 10 | |
| 2.71.1 | 0 / 10 | |
| 2.71.0 | 0 / 10 | |
| 2.70.2 | 0 / 10 | |
| 2.70.1 | 0 / 10 | |
| 2.70.0 | 0 / 10 |
v2.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.3
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.2
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.1
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.97.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.1
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.2
3 findingsThis version was published by a different npm account than previous versions on 2026-01-05. This could indicate a legitimate maintainer transition or an account compromise.
[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.3
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.2
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.1
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.1
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Publisher semi-bot is SPAM-FLAGGED; generalizes to all versions published under this account.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: semi-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.