@propellerads/pagination
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Org-published UI component; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@propellerads/arrow-button | AI (dependencies): Internal sibling package from same org/monorepo; consistent with the component library pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped UI component library; missing description is cosmetic, not a risk indicator for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 4 / 6 | |
| 2.0.4 | 4 / 5 | |
| 2.0.3 | 4 / 5 | |
| 2.0.2 | 4 / 5 | |
| 2.0.1 | 4 / 5 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package 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.