← Home

@86d-app/storage

npm Repository Homepage

<p align="center"> <a href="https://86d.app"> <img src="https://86d.app/logo" height="96" alt="86d" /> </a> </p>

10
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

imsanchez

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Fires in a security test asserting path traversal is blocked; not credential harvesting. ai

Versions (showing 10 of 10)

Version Deps Published
0.0.30 1 / 5
0.0.26 1 / 5
0.0.25 1 / 5
0.0.24 1 / 5
0.0.23 1 / 5
0.0.22 1 / 5
0.0.21 1 / 5
0.0.19 1 / 5
0.0.18 1 / 5
0.0.17 1 / 5

v0.0.30

3 findings
HIGH etc-passwd-access: src/__tests__/local.test.ts:109 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/86d-app/86d/blob/f5c3606cdb3fd160b7cda8b1375e0aa40aec6b12/src/__tests__/local.test.ts#L109 107 | it("rejects path traversal in delete", async () => { 108 | await expect( > 109 | provider.delete({ key: "../../../etc/passwd" }), 110 | ).rejects.toThrow("path traversal"); 111 | });

HIGH etc-passwd-access: src/__tests__/local.test.ts:128 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/86d-app/86d/blob/f5c3606cdb3fd160b7cda8b1375e0aa40aec6b12/src/__tests__/local.test.ts#L128 126 | await expect( 127 | provider.upload({ > 128 | key: "stores/abc/../../../../../../../etc/passwd", 129 | content: Buffer.from("malicious"), 130 | contentType: "text/plain",

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.0.26

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.0.25

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.0.24

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.0.23

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.0.22

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.0.21

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.0.19

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.0.18

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.0.17

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.