@semcore/feedback-form
Semrush Feedback Form 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/link | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@semcore/modal | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@semcore/button | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@semcore/notice | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@semcore/illustration | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@semcore/notice-bubble | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@semcore/spin-container | AI (dependencies): Sibling @semcore monorepo package; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:final-form | AI (phantom-deps): final-form is a declared runtime dep used transitively via react-final-form; false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 15 / 5 | |
| 17.1.0 | 15 / 5 | |
| 17.0.1 | 15 / 5 | |
| 17.0.0 | 15 / 5 | |
| 16.3.1 | 17 / 3 | |
| 16.3.0 | 17 / 3 | |
| 16.2.1 | 17 / 3 | |
| 16.2.0 | 17 / 3 | |
| 16.1.12 | 17 / 3 |
v17.2.0
1 findingPackage 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.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.