← Home

@uploadcare/blocks

npm Repository Homepage
19
Versions
—
License
No
Install Scripts
Missing
Provenance

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

eadidenkorsedykhuploadcare-usernd0ut

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

Versions (showing 19 of 19)

Version Deps Published
0.50.4 4 / 37
0.50.3 4 / 37
0.50.2 4 / 37
0.50.1 4 / 37
0.50.0 4 / 37
0.49.0 4 / 37
0.48.1 4 / 37
0.48.0 4 / 37
0.47.0 4 / 37
0.46.3 4 / 37
0.46.2 4 / 37
0.46.1 4 / 37
0.46.0 4 / 37
0.45.0 3 / 37
0.44.0 3 / 37
0.43.0 3 / 37
0.42.1 3 / 37
0.41.1 3 / 37
0.41.0 3 / 37

v0.50.3

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 2024-08-05, known maintainer) provenance

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

v0.50.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: uploadcare-user → nd0ut (on 2024-08-05, known maintainer) provenance

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

v0.50.1

1 finding
LOW No provenance attestation provenance

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

v0.50.0

1 finding
LOW No provenance attestation provenance

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

v0.49.0

1 finding
LOW No provenance attestation provenance

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

v0.48.1

1 finding
LOW No provenance attestation provenance

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

v0.48.0

1 finding
LOW No provenance attestation provenance

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

v0.47.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 2024-06-25, known maintainer) provenance

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

v0.46.3

1 finding
LOW No provenance attestation provenance

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

v0.46.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 2024-07-01, known maintainer) provenance

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

v0.46.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: nd0ut → uploadcare-user (on 2024-06-28, known maintainer) provenance

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

v0.46.0

1 finding
LOW No provenance attestation provenance

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

v0.45.0

1 finding
LOW No provenance attestation provenance

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

v0.44.0

1 finding
LOW No provenance attestation provenance

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

v0.43.0

1 finding
LOW No provenance attestation provenance

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

v0.42.1

1 finding
LOW No provenance attestation provenance

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

v0.41.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.

v0.41.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.