@semcore/accordion
Semrush Accordion 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/flex-box | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@semcore/animation | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@semcore/button | AI (phantom-deps): Same-org @semcore scope; declared as dep, likely re-exported or used indirectly in build output. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 3 / 4 | |
| 17.1.0 | 3 / 4 | |
| 17.0.2 | 3 / 4 | |
| 17.0.1 | 3 / 4 | |
| 17.0.0 | 3 / 4 | |
| 16.8.1 | 6 / 2 | |
| 16.8.0 | 6 / 2 | |
| 16.7.2 | 6 / 2 | |
| 5.49.0 | 6 / 2 |
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.2
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.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.