@semcore/input-tags
Semrush InputTags 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@semcore/portal | AI (phantom-deps): Same-org sibling; likely re-exported transitively, not a direct import. | ai | |
| phantom-deps | phantom-dep:@semcore/flex-box | AI (phantom-deps): Same-org sibling; likely re-exported transitively, not a direct import. | ai | |
| phantom-deps | phantom-dep:@semcore/scroll-area | AI (phantom-deps): Same-org sibling; likely re-exported transitively, not a direct import. | ai | |
| provenance | no-provenance | AI (provenance): Semrush intergalactic monorepo consistently publishes without Sigstore provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@semcore/tag | AI (dependencies): First-party Semrush monorepo sibling package; same publisher and ecosystem as this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 2 / 8 | |
| 17.1.0 | 2 / 8 | |
| 17.0.1 | 2 / 8 | |
| 17.0.0 | 2 / 8 | |
| 16.1.1 | 5 / 8 | |
| 16.1.0 | 5 / 8 | |
| 16.0.13 | 5 / 8 | |
| 4.48.0 | 6 / 8 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.