← Home

@kne/react-file

npm Repository Homepage
45
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

lingtongyangwang123456juliewangmetacoo

Keywords

reactfileuploadpreviewdownloadfile-systemimageavatarantdi18nofficepdfzip

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New dep is same-org first-party package, consistent with existing @kne dependency tree. ai
dependencies unvetted-dep:@extend-ai/react-docx AI (dependencies): Docx render dep consistent with file-preview library's function. ai
dependencies unvetted-dep:@extend-ai/react-xlsx AI (dependencies): Xlsx render dep consistent with file-preview library's function. ai
phantom-deps phantom-dep:@docmentis/udoc-viewer AI (phantom-deps): Config-referenced viewer dep, consistent with package's file-preview purpose. ai

Versions (showing 45 of 45)

Version Deps Published
0.1.44 23 / 8
0.1.43 22 / 8
0.1.42 22 / 8
0.1.41 22 / 8
0.1.40 22 / 8
0.1.39 22 / 8
0.1.38 22 / 8
0.1.37 21 / 8
0.1.36 19 / 8
0.1.35 18 / 8
0.1.34 17 / 8
0.1.33 17 / 8
0.1.32 17 / 8
0.1.31 17 / 8
0.1.30 16 / 8
0.1.29 16 / 8
0.1.28 16 / 8
0.1.27 16 / 8
0.1.26 16 / 8
0.1.25 16 / 8
0.1.24 16 / 8
0.1.23 16 / 8
0.1.22 16 / 8
0.1.21 16 / 8
0.1.20 16 / 8
0.1.19 16 / 8
0.1.18 16 / 8
0.1.17 16 / 8
0.1.16 16 / 8
0.1.15 16 / 8
0.1.14 16 / 8
0.1.13 15 / 8
0.1.12 14 / 8
0.1.11 14 / 8
0.1.10 14 / 8
0.1.9 14 / 8
0.1.8 14 / 8
0.1.7 14 / 8
0.1.6 14 / 8
0.1.5 14 / 8
0.1.4 14 / 8
0.1.3 14 / 8
0.1.2 14 / 8
0.1.1 14 / 8
0.1.0 14 / 8

v0.1.44

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.43

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.42

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.41

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.40

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.39

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.38

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

1 finding
LOW No provenance attestation provenance

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

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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