@uploadcare/file-uploader

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

uploadcare-usernd0utrsedykheadidenko

Keywords

web componentsuploadcarelighterfile uploaderadaptive imageimage optimizationimage editingimage sizecloud image editorsymbiote.jsupload api clientbuilding blocksblockslr-blocksuc-blockswidgetintegrationsfrontendtypescriptsmart cdncloud file platformtransformation apiwebpavifcustom elementsshadow domshadow rootcss context propertiesmeta applicationsMIT

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	2026/05/12
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	2026/05/12
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	2026/04/30
phantom-deps	phantom-dep:keyux	AI (phantom-deps): keyux is a declared runtime dep; phantom-dep heuristic false positive for this bundled package.	ai	2026/04/30
phantom-deps	phantom-dep:@uploadcare/image-shrink	AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this bundled package.	ai	2026/04/30
phantom-deps	phantom-dep:@uploadcare/cname-prefix	AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this bundled package.	ai	2026/04/30
phantom-deps	phantom-dep:nanostores	AI (phantom-deps): nanostores is a declared runtime dep; phantom-dep heuristic false positive for this bundled package.	ai	2026/04/30

Versions (showing 43 of 43)

Version	Deps	Published
1.31.0	8 / 46	2026-06-03
1.30.2	8 / 46	2026-06-01
1.30.1	8 / 46	2026-05-27
1.30.0	8 / 46	2026-05-27
1.29.1	8 / 46	2026-04-30
1.29.0	8 / 46	2026-04-22
1.28.0	8 / 46	2026-04-03
1.27.3	8 / 46	2026-04-02
1.27.2	8 / 46	2026-03-23
1.27.1	8 / 46	2026-02-16
1.27.0	8 / 46	2026-02-11
1.26.3	8 / 46	2026-02-04
1.26.2	8 / 46	2026-02-02
1.26.1	8 / 46	2026-01-29
1.26.0	8 / 46	2026-01-27
1.25.0	6 / 37	2026-01-15
1.24.8	6 / 37	2026-01-13
1.24.7	6 / 37	2025-12-25
1.24.6	6 / 37	2025-12-23
1.24.5	6 / 37	2025-12-01
1.24.4	6 / 36	2025-11-21
1.24.3	6 / 36	2025-11-06
1.24.2	6 / 36	2025-11-05
1.24.1	6 / 36	2025-10-30
1.24.0	6 / 36	2025-10-28
1.23.1	6 / 39	2025-10-24
1.23.0	6 / 39	2025-10-07
1.22.0	6 / 39	2025-09-26
1.21.0	6 / 39	2025-09-10
1.20.1	5 / 39	2025-08-27
1.20.0	5 / 39	2025-08-26
1.19.5	5 / 39	2025-08-21
1.19.4	5 / 39	2025-07-30
1.19.3	5 / 39	2025-07-15
1.19.2	5 / 39	2025-07-10
1.19.1	5 / 39	2025-07-08
1.19.0	5 / 39	2025-07-07
1.18.0	4 / 39	2025-06-23
1.17.2	4 / 39	2025-06-18
1.17.1	4 / 39	2025-06-18
1.17.0	4 / 39	2025-06-16
1.16.2	4 / 33	2025-05-07
1.16.1	4 / 33	2025-05-06

v1.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.30.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: nd0ut → uploadcare-user (on 2026-06-01, known maintainer) provenance

This version was published by a different npm account (uploadcare-user) than the most recent previously approved version (nd0ut) on 2026-06-01, 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.30.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: uploadcare-user → nd0ut (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (nd0ut) than the most recent previously approved version (uploadcare-user) on 2026-05-27, 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.30.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: uploadcare-user → nd0ut (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (nd0ut) than the most recent previously approved version (uploadcare-user) on 2026-05-27, 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.29.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.27.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.27.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.27.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.24.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.24.1

3 findings

HIGH New obfuscated file: dist/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/index.ssr.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.24.0

3 findings

HIGH New obfuscated file: dist/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/index.ssr.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.