← Home

@flowrag/storage-s3

6
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

zweer

Keywords

flowragragtypescriptstoragekvs3aws

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@aws-sdk/client-s3 AI (phantom-deps): Framework-scoped AWS SDK package; loaded by convention, not direct import. ai
phantom-deps phantom-dep:@flowrag/core AI (phantom-deps): Same-org monorepo dependency; declared and used via convention. ai
dependencies unvetted-dep:@flowrag/core AI (dependencies): Internal monorepo sibling dependency; expected coupling for this package family. ai

Versions (showing 6 of 6)

Version Deps Published
0.3.4 2 / 0
0.3.3 2 / 0
0.3.2 2 / 0
0.3.1 2 / 0
0.3.0 2 / 0
0.1.0 2 / 0

v0.3.4

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

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

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

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

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