@douyinfe/semi-icons
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
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 2.101.1 | 1 / 16 | |
| 2.100.0 | 1 / 16 | |
| 2.99.3 | 1 / 16 | |
| 2.99.2 | 1 / 16 | |
| 2.99.1 | 1 / 16 | |
| 2.99.0 | 1 / 16 | |
| 2.98.0 | 1 / 16 | |
| 2.97.0 | 1 / 16 | |
| 2.96.1 | 1 / 16 | |
| 2.96.0 | 1 / 16 | |
| 2.94.0 | 1 / 16 | |
| 2.87.1 | 1 / 16 | |
| 2.87.0 | 1 / 16 | |
| 2.86.0 | 1 / 16 | |
| 2.85.0 | 1 / 16 | |
| 2.84.0 | 1 / 16 | |
| 2.83.0 | 1 / 16 | |
| 2.82.1 | 1 / 16 | |
| 2.82.0 | 1 / 16 | |
| 2.81.0 | 1 / 16 | |
| 2.80.0 | 1 / 16 | |
| 2.79.0 | 1 / 16 | |
| 2.78.0 | 1 / 16 | |
| 2.77.1 | 1 / 16 | |
| 2.77.0 | 1 / 16 | |
| 2.76.1 | 1 / 16 | |
| 2.76.0 | 1 / 16 | |
| 2.75.0 | 1 / 16 | |
| 2.74.0 | 1 / 16 | |
| 2.73.0 | 1 / 16 | |
| 2.72.3 | 1 / 16 | |
| 2.72.2 | 1 / 16 | |
| 2.72.1 | 1 / 16 | |
| 2.72.0 | 1 / 16 | |
| 2.71.3 | 1 / 16 | |
| 2.71.2 | 1 / 16 | |
| 2.71.1 | 1 / 16 | |
| 2.71.0 | 1 / 16 | |
| 2.0.8 | 2 / 13 | |
| 2.0.7 | 2 / 13 | |
| 2.0.6 | 1 / 13 | |
| 2.0.5 | 1 / 13 | |
| 2.0.4 | 1 / 13 | |
| 2.0.3 | 1 / 13 | |
| 2.0.2 | 1 / 13 | |
| 2.0.1 | 1 / 13 | |
| 2.0.0 | 1 / 13 |
v2.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.94.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.