@scena/dragscroll
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@scena/event-emitter | AI (dependencies): Sibling package in the same @scena org by the same author (daybrush/younkue); stable dependency across versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 2 / 10 | |
| 1.3.0 | 2 / 10 | |
| 1.2.2 | 2 / 10 | |
| 1.2.1 | 2 / 10 | |
| 1.2.0 | 2 / 10 | |
| 1.1.1 | 2 / 10 | |
| 1.1.0 | 2 / 10 | |
| 1.0.3 | 2 / 10 | |
| 1.0.2 | 1 / 10 | |
| 1.0.1 | 1 / 10 | |
| 1.0.0 | 1 / 10 |
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.