← Home

@ckbox/uploader

npm Homepage

CKBox upload widget

7
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

cksource

Keywords

file managerckeditorfile uploadimage uploaduploadfilesdrag and dropmultilingualcomponentreactuploaderrescaling imagesresponsive imageswebpapicross-domainimage editingmulti-tenant application

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:react AI (phantom-deps): React is a peer dependency for this component library; loaded by convention. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): React-dom is a peer dependency for this component library; loaded by convention. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): Type package loaded by convention for React peer dependency. ai
phantom-deps phantom-dep:@types/react-dom AI (phantom-deps): Type package loaded by convention for React-dom peer dependency. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): Known implicit runtime dependency; stable across versions. ai

Versions (showing 7 of 7)

Version Deps Published
2.11.1 6 / 0
2.11.0 6 / 0
2.10.1 6 / 0
2.10.0 6 / 0
2.9.2 6 / 0
2.9.1 6 / 0
2.9.0 6 / 0

v2.11.1

1 finding
LOW No provenance attestation provenance

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

v2.11.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.

v2.10.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.

v2.10.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.

v2.9.2

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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

v2.9.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.