← Home

@quatrain/cloudwrapper

npm Repository Homepage

Cloud wrappers commons

27
Versions
AGPL-3.0-only
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

crapougnaxelliottlepine

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is offset by Sigstore CI/CD attestation. ai
license copyleft-license:AGPL-3.0-only AI (license): AGPL-3.0 is the declared license for this package family; stable across versions. ai

Versions (showing 27 of 27)

Version Deps Published
1.2.3 3 / 10
1.2.1 3 / 10
1.1.27 3 / 10
1.1.26 3 / 10
1.1.25 3 / 10
1.1.24 3 / 10
1.1.23 3 / 10
1.1.22 3 / 10
1.1.21 3 / 10
1.1.20 3 / 10
1.1.19 3 / 10
1.1.18 3 / 10
1.1.17 3 / 10
1.1.16 3 / 10
1.1.15 3 / 10
1.1.14 1 / 10
1.1.13 0 / 10
1.1.12 0 / 10
1.1.11 0 / 10
1.1.10 0 / 10
1.1.9 0 / 10
1.1.8 0 / 10
1.1.7 0 / 10
1.1.6 0 / 10
1.1.5 0 / 10
1.0.1 0 / 11
1.0.0 0 / 11

v1.2.3

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.

v1.1.14

1 finding
LOW No provenance attestation provenance

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

v1.1.13

1 finding
LOW No provenance attestation provenance

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

v1.1.12

1 finding
LOW No provenance attestation provenance

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

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.10

1 finding
LOW No provenance attestation provenance

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

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.8

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.0.1

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.