@blocklet/uploader
blocklet upload 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, 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:@lottiefiles/react-lottie-player | AI (dependencies): Popular Lottie animation React player; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/dashboard | AI (dependencies): Well-known Uppy dashboard UI; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/drag-drop | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/file-input | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@blocklet/ui-react | AI (dependencies): Same org (arcblock/blocklet); expected internal dependency. | ai | |
| dependencies | unvetted-dep:@uppy/image-editor | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/progress-bar | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/provider-views | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/golden-retriever | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/status-bar | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/drop-target | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/tus | AI (dependencies): Well-known Uppy file upload library; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/url | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/core | AI (dependencies): Well-known Uppy core library; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/react | AI (dependencies): Well-known Uppy React integration; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/webcam | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:react-player | AI (dependencies): Popular React media player component; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/locales | AI (dependencies): Well-known Uppy locales package; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@uppy/unsplash | AI (dependencies): Well-known Uppy plugin; stable ecosystem package. | ai | |
| phantom-deps | phantom-dep:react-player | AI (phantom-deps): react-player is a declared dependency; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@uppy/file-input | AI (phantom-deps): Declared dependency; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@uppy/progress-bar | AI (phantom-deps): Declared dependency; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@uppy/golden-retriever | AI (phantom-deps): Declared dependency; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:ufo | AI (phantom-deps): Declared dependency; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mui/utils | AI (phantom-deps): Declared dependency; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Declared dependency; phantom-dep is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 31 of 131)
| Version | Deps | Published |
|---|---|---|
| 0.1.29 | 41 / 14 | |
| 0.1.28 | 40 / 14 | |
| 0.1.27 | 40 / 14 | |
| 0.1.26 | 40 / 14 | |
| 0.1.25 | 40 / 14 | |
| 0.1.24 | 40 / 14 | |
| 0.1.23 | 40 / 14 | |
| 0.1.22 | 40 / 14 | |
| 0.1.21 | 40 / 14 | |
| 0.1.20 | 39 / 14 | |
| 0.1.19 | 39 / 14 | |
| 0.1.18 | 39 / 14 | |
| 0.1.17 | 39 / 14 | |
| 0.1.16 | 39 / 14 | |
| 0.1.15 | 39 / 14 | |
| 0.1.14 | 39 / 14 | |
| 0.1.13 | 39 / 14 | |
| 0.1.11 | 39 / 14 | |
| 0.1.10 | 39 / 14 | |
| 0.1.9 | 39 / 14 | |
| 0.1.8 | 39 / 14 | |
| 0.1.6 | 39 / 14 | |
| 0.1.4 | 39 / 14 | |
| 0.1.3 | 39 / 14 | |
| 0.1.2 | 39 / 14 | |
| 0.1.1 | 39 / 14 | |
| 0.0.8 | 26 / 12 | |
| 0.0.7 | 26 / 12 | |
| 0.0.6 | 26 / 12 | |
| 0.0.5 | 26 / 12 | |
| 0.0.4 | 26 / 12 |
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.