@adobe/helix-shared-tokencache
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 2 / 1 | |
| 1.6.0 | 2 / 1 | |
| 1.5.4 | 2 / 1 | |
| 1.5.3 | 2 / 1 | |
| 1.5.2 | 2 / 1 | |
| 1.5.1 | 2 / 1 | |
| 1.5.0 | 2 / 1 | |
| 1.4.45 | 2 / 1 | |
| 1.4.44 | 2 / 1 | |
| 1.4.43 | 2 / 1 | |
| 1.4.42 | 2 / 1 | |
| 1.4.41 | 2 / 1 | |
| 1.4.40 | 2 / 1 | |
| 1.4.39 | 2 / 1 | |
| 1.4.38 | 2 / 1 | |
| 1.4.37 | 2 / 1 | |
| 1.4.36 | 2 / 1 | |
| 1.4.35 | 2 / 1 | |
| 1.4.34 | 2 / 1 | |
| 1.4.33 | 2 / 1 | |
| 1.4.32 | 2 / 1 | |
| 1.4.31 | 2 / 1 | |
| 1.4.30 | 2 / 1 | |
| 1.4.29 | 2 / 1 | |
| 1.4.28 | 2 / 1 | |
| 1.4.27 | 2 / 1 | |
| 1.4.26 | 2 / 1 | |
| 1.4.25 | 2 / 1 | |
| 1.4.24 | 2 / 1 | |
| 1.4.23 | 2 / 1 | |
| 1.4.22 | 2 / 1 | |
| 1.4.21 | 2 / 1 | |
| 1.4.20 | 2 / 1 | |
| 1.4.19 | 2 / 1 | |
| 1.4.18 | 2 / 1 | |
| 1.4.17 | 2 / 1 | |
| 1.4.16 | 2 / 1 | |
| 1.4.15 | 2 / 1 | |
| 1.4.14 | 2 / 1 | |
| 1.4.13 | 2 / 1 | |
| 1.4.12 | 2 / 1 | |
| 1.4.11 | 2 / 1 | |
| 1.4.10 | 2 / 1 | |
| 1.4.9 | 2 / 1 | |
| 1.4.8 | 2 / 1 | |
| 1.4.7 | 2 / 1 | |
| 1.4.6 | 2 / 1 | |
| 1.4.5 | 2 / 1 | |
| 1.4.4 | 2 / 1 |
v1.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.