@jskit-ai/uploads-image-web
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:@uppy/compressor | AI (dependencies): @uppy/compressor is part of the well-known Uppy ecosystem; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is cosmetic, not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package under active development; sparse metadata is a style choice, not a spam/malware indicator. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.1.63 | 6 / 0 | |
| 0.1.62 | 6 / 0 | |
| 0.1.61 | 6 / 0 | |
| 0.1.60 | 6 / 0 | |
| 0.1.59 | 6 / 0 | |
| 0.1.44 | 6 / 0 | |
| 0.1.43 | 6 / 0 | |
| 0.1.41 | 6 / 0 | |
| 0.1.38 | 6 / 0 | |
| 0.1.37 | 6 / 0 | |
| 0.1.35 | 6 / 0 | |
| 0.1.33 | 6 / 0 | |
| 0.1.32 | 6 / 0 | |
| 0.1.28 | 6 / 0 | |
| 0.1.25 | 6 / 0 | |
| 0.1.23 | 6 / 0 | |
| 0.1.22 | 6 / 0 | |
| 0.1.21 | 6 / 0 | |
| 0.1.20 | 6 / 0 | |
| 0.1.19 | 6 / 0 | |
| 0.1.17 | 6 / 0 | |
| 0.1.15 | 6 / 0 | |
| 0.1.14 | 6 / 0 | |
| 0.1.10 | 6 / 0 | |
| 0.1.2 | 6 / 0 | |
| 0.1.1 | 6 / 0 |
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.