@blocklet/uploader-server
blocklet upload server
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@abtnode/cron | AI (dependencies): Same org (ArcBlock/ABTNode) as the package publisher; internal dependency. | ai | |
| dependencies | unvetted-dep:@tus/server | AI (dependencies): Well-known tus protocol server library; legitimate dependency for an uploader package. | ai | |
| dependencies | unvetted-dep:@tus/file-store | AI (dependencies): Official tus file-store companion; legitimate for an uploader server. | ai | |
| dependencies | unvetted-dep:@uppy/companion | AI (dependencies): Official Uppy companion server; expected dependency for an uploader package. | ai | |
| dependencies | unvetted-dep:exif-be-gone | AI (dependencies): Known EXIF stripping library; appropriate for an image uploader server. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (62 approved, 0 rejected); version diff shows no material changes, reducing takeover risk. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals elevate this. | ai | |
| phantom-deps | phantom-dep:@blocklet/constant | AI (phantom-deps): Same org scope; likely used indirectly via re-exports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ufo | AI (phantom-deps): ufo is declared as a dependency and used transitively; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.3.19 | 18 / 11 | |
| 0.3.16 | 18 / 11 | |
| 0.3.15 | 18 / 11 | |
| 0.3.14 | 18 / 11 | |
| 0.3.13 | 18 / 11 | |
| 0.3.11 | 18 / 11 | |
| 0.3.9 | 18 / 11 | |
| 0.3.8 | 18 / 11 | |
| 0.3.7 | 18 / 11 | |
| 0.3.5 | 18 / 11 | |
| 0.3.4 | 18 / 11 | |
| 0.3.3 | 18 / 11 | |
| 0.3.2 | 18 / 11 | |
| 0.3.1 | 18 / 11 | |
| 0.3.0 | 18 / 11 | |
| 0.2.15 | 18 / 11 | |
| 0.2.14 | 18 / 11 | |
| 0.2.13 | 18 / 11 | |
| 0.2.12 | 18 / 11 | |
| 0.2.11 | 18 / 11 | |
| 0.2.10 | 18 / 11 | |
| 0.2.9 | 18 / 11 | |
| 0.2.8 | 18 / 11 | |
| 0.2.7 | 18 / 11 | |
| 0.2.6 | 18 / 11 | |
| 0.2.5 | 18 / 11 | |
| 0.2.4 | 18 / 11 | |
| 0.2.3 | 18 / 11 | |
| 0.2.2 | 18 / 11 | |
| 0.2.1 | 18 / 11 | |
| 0.2.0 | 18 / 11 | |
| 0.1.102 | 18 / 11 | |
| 0.1.96 | 17 / 11 |
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.