@adobe/helix-config-storage
Helix Config Storage
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Adobe org package published via GitHub Actions CI; dormancy consistent with normal maintenance cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@adobe/helix-shared-string | AI (dependencies): Same Adobe org scope; consistent with other helix-shared-* deps used throughout this package family. | ai | |
| provenance | no-provenance | AI (provenance): Adobe CI-published package; provenance absence is consistent across the org's packages and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@adobe/fetch | AI (phantom-deps): Same-org dep likely used transitively through @adobe/helix-shared-* packages; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@adobe/helix-shared-utils | AI (phantom-deps): Same-org dep; stable FP for this Adobe Helix package. | ai | |
| phantom-deps | phantom-dep:@adobe/helix-shared-config | AI (phantom-deps): Same-org dep; stable FP for this Adobe Helix package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 11 / 18 | |
| 3.1.0 | 11 / 18 | |
| 3.0.1 | 11 / 18 | |
| 3.0.0 | 11 / 18 | |
| 2.14.1 | 11 / 18 | |
| 2.14.0 | 11 / 18 | |
| 2.13.6 | 11 / 18 | |
| 2.13.5 | 11 / 18 | |
| 2.13.4 | 11 / 18 | |
| 2.13.3 | 11 / 18 | |
| 2.13.2 | 11 / 18 | |
| 2.13.1 | 11 / 18 | |
| 2.12.2 | 11 / 18 | |
| 2.12.1 | 10 / 18 | |
| 2.12.0 | 10 / 18 | |
| 2.11.0 | 10 / 18 | |
| 2.10.9 | 10 / 18 | |
| 2.10.8 | 10 / 18 | |
| 2.10.7 | 10 / 18 | |
| 2.10.6 | 10 / 18 | |
| 2.10.5 | 10 / 18 | |
| 2.10.4 | 10 / 18 | |
| 2.10.3 | 10 / 18 | |
| 2.10.2 | 10 / 18 | |
| 2.10.0 | 10 / 18 | |
| 2.9.0 | 10 / 18 | |
| 2.8.5 | 10 / 18 | |
| 2.8.4 | 10 / 18 | |
| 2.8.3 | 10 / 18 | |
| 2.8.2 | 10 / 18 | |
| 2.8.1 | 10 / 18 | |
| 2.6.0 | 10 / 18 | |
| 2.5.2 | 10 / 18 | |
| 2.5.1 | 10 / 18 | |
| 2.5.0 | 10 / 18 | |
| 2.4.0 | 10 / 18 | |
| 2.3.0 | 10 / 18 | |
| 2.2.13 | 9 / 18 | |
| 2.2.12 | 9 / 18 | |
| 2.2.11 | 9 / 18 | |
| 2.2.10 | 9 / 18 | |
| 2.2.9 | 9 / 18 | |
| 2.2.8 | 9 / 17 | |
| 2.2.7 | 9 / 17 | |
| 2.2.6 | 9 / 17 | |
| 2.2.5 | 9 / 17 | |
| 2.2.4 | 9 / 17 | |
| 2.2.3 | 9 / 17 | |
| 2.2.2 | 9 / 17 | |
| 2.2.1 | 9 / 17 |
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.