← Home

@uploadcare/react-uploader

npm Repository Homepage

React component for file uploads using Uploadcare

24
Versions
MIT
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

uploadcare-usernd0utrsedykheadidenko

Keywords

uploadcarereactcomponentwidgetuploaderfile-uploaderimage-uploaderupload-componentupload filemultipart-uploadimage-pickerreact-image-pickerreact-uploadreact-upload-componentreact-file-upload-componentfilepickerfile-pickerfile-uploadfile uploadingfileuploadinputdropzonemultimultipartajaxxhrdialogstorefilesimageimagesuse file uploadreact file uploadreact hook file uploadfront-end

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Publisher is the official Uploadcare org account with prior approvals; dormancy likely reflects org publishing cadence, not takeover. ai
phantom-deps phantom-dep:@uploadcare/react-adapter AI (phantom-deps): Same-org dependency; phantom-dep false positive common for re-exported peer deps in this package structure. ai

Versions (showing 24 of 24)

Version Deps Published
1.17.0 2 / 4
1.16.0 2 / 4
1.15.0 2 / 4
1.14.0 2 / 4
1.13.0 2 / 4
1.12.0 2 / 4
1.11.2 2 / 4
1.11.1 2 / 4
1.11.0 2 / 4
1.10.2 2 / 0
1.10.1 2 / 0
1.10.0 2 / 0
1.9.0 2 / 0
1.8.1 2 / 0
1.8.0 2 / 0
1.7.1 2 / 0
1.7.0 2 / 0
1.6.0 2 / 0
1.5.0 2 / 0
1.4.0 2 / 0
1.3.0 2 / 0
1.2.0 2 / 0
1.1.0 2 / 0
1.0.0 2 / 0

v1.17.0

1 finding
LOW No provenance attestation provenance

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

v1.7.1

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.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.