@semcore/widget-empty
Semrush WidgetEmpty Component
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@semcore/illustration | AI (dependencies): Same-org monorepo sibling dependency; stable pattern across all @semcore/* packages. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @semcore/* releases; no provenance is the norm for this publisher. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 1 / 3 | |
| 17.1.0 | 1 / 3 | |
| 17.0.1 | 1 / 3 | |
| 17.0.0 | 1 / 3 | |
| 16.1.1 | 2 / 2 | |
| 16.1.0 | 2 / 2 | |
| 4.44.0 | 3 / 2 |
v17.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.