← Home

@adobe/helix-shared-storage

npm Repository Homepage
38
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

marbectripodgarthdblazdadobe-adminpatrickfultontrieloffkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergrofekptdobeadobehallsfullcolorcoderdjaeggidylandepassmhaackamol-anandstopp-adobenamaroradotenduh_schmidtasthabh23zdahbituicufmeschbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Adobe org migrated to GitHub Actions publishing with SLSA attestation; this is the expected CI/CD transition pattern. ai

Versions (showing 38 of 38)

Version Deps Published
2.1.4 5 / 2
2.1.3 5 / 2
2.1.2 5 / 2
2.1.1 5 / 2
2.1.0 5 / 2
2.0.1 5 / 2
2.0.0 5 / 2
1.12.1 5 / 2
1.12.0 5 / 2
1.11.0 5 / 2
1.10.2 5 / 2
1.10.1 5 / 2
1.10.0 5 / 2
1.9.1 5 / 2
1.9.0 5 / 2
1.8.0 5 / 2
1.7.1 5 / 2
1.7.0 5 / 2
1.6.0 5 / 2
1.5.0 5 / 2
1.4.2 5 / 2
1.4.1 5 / 2
1.4.0 5 / 2
1.3.1 5 / 2
1.3.0 5 / 2
1.2.0 5 / 2
1.1.2 5 / 2
1.1.1 5 / 2
1.1.0 5 / 2
1.0.9 5 / 2
1.0.8 5 / 2
1.0.7 5 / 2
1.0.6 5 / 2
1.0.5 5 / 2
1.0.4 5 / 2
1.0.3 5 / 2
1.0.2 5 / 2
1.0.1 5 / 2

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.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.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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.

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