@uploadcare/file-uploader
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard minified build output for this package; MIT license header and readable imports confirm legitimate bundling. | ai | |
| source-diff | obfuscated-file:dist/index.ssr.js | AI (source-diff): SSR stub file with readable class stubs; minification is expected for this package's build output. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): @lit/context is a declared runtime dep; phantom-dep heuristic false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:keyux | AI (phantom-deps): keyux is a declared runtime dep; phantom-dep heuristic false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@uploadcare/image-shrink | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@uploadcare/cname-prefix | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:nanostores | AI (phantom-deps): nanostores is a declared runtime dep; phantom-dep heuristic false positive for this bundled package. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.32.0 | 8 / 46 | |
| 1.31.2 | 8 / 46 | |
| 1.31.1 | 8 / 46 | |
| 1.31.0 | 8 / 46 | |
| 1.30.2 | 8 / 46 | |
| 1.30.1 | 8 / 46 | |
| 1.30.0 | 8 / 46 | |
| 1.29.1 | 8 / 46 | |
| 1.29.0 | 8 / 46 | |
| 1.28.0 | 8 / 46 | |
| 1.27.3 | 8 / 46 | |
| 1.27.2 | 8 / 46 | |
| 1.27.1 | 8 / 46 | |
| 1.27.0 | 8 / 46 | |
| 1.26.3 | 8 / 46 | |
| 1.26.2 | 8 / 46 | |
| 1.26.1 | 8 / 46 | |
| 1.26.0 | 8 / 46 | |
| 1.25.0 | 6 / 37 | |
| 1.24.8 | 6 / 37 | |
| 1.24.7 | 6 / 37 | |
| 1.24.6 | 6 / 37 | |
| 1.24.5 | 6 / 37 | |
| 1.24.4 | 6 / 36 | |
| 1.24.3 | 6 / 36 | |
| 1.24.2 | 6 / 36 | |
| 1.24.1 | 6 / 36 | |
| 1.24.0 | 6 / 36 | |
| 1.23.1 | 6 / 39 | |
| 1.23.0 | 6 / 39 | |
| 1.22.0 | 6 / 39 | |
| 1.21.0 | 6 / 39 | |
| 1.20.1 | 5 / 39 | |
| 1.20.0 | 5 / 39 | |
| 1.19.5 | 5 / 39 | |
| 1.19.4 | 5 / 39 | |
| 1.19.3 | 5 / 39 | |
| 1.19.2 | 5 / 39 | |
| 1.19.1 | 5 / 39 | |
| 1.19.0 | 5 / 39 | |
| 1.18.0 | 4 / 39 | |
| 1.17.2 | 4 / 39 | |
| 1.17.1 | 4 / 39 | |
| 1.17.0 | 4 / 39 | |
| 1.16.2 | 4 / 33 | |
| 1.16.1 | 4 / 33 | |
| 1.16.0 | 4 / 33 | |
| 1.15.0 | 4 / 33 | |
| 1.14.0 | 4 / 32 | |
| 1.13.2 | 4 / 32 | |
| 1.13.1 | 4 / 37 | |
| 1.13.0 | 4 / 37 | |
| 1.12.1 | 4 / 37 | |
| 1.12.0 | 4 / 37 | |
| 1.11.3 | 4 / 37 | |
| 1.11.2 | 4 / 37 | |
| 1.11.1 | 4 / 37 | |
| 1.11.0 | 4 / 37 | |
| 1.10.0 | 4 / 37 | |
| 1.9.0 | 4 / 37 | |
| 1.8.1 | 4 / 37 | |
| 1.8.0 | 4 / 37 | |
| 1.7.0 | 4 / 37 | |
| 1.6.0 | 4 / 37 | |
| 1.5.2 | 4 / 37 | |
| 1.5.1 | 4 / 37 | |
| 1.5.0 | 4 / 37 | |
| 1.4.0 | 4 / 37 | |
| 1.3.0 | 4 / 37 | |
| 1.2.0 | 4 / 37 | |
| 1.1.1 | 4 / 37 | |
| 1.1.0 | 4 / 37 | |
| 1.0.0 | 4 / 37 |
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (uploadcare-user) than the most recent previously approved version (nd0ut) on 2024-12-12, but uploadcare-user is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (uploadcare-user) than the most recent previously approved version (nd0ut) on 2024-12-04, but uploadcare-user is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nd0ut) than the most recent previously approved version (uploadcare-user) on 2024-12-04, but nd0ut is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.