@descope/sdk-helpers
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 1 / 41 | |
| 0.8.0 | 1 / 41 | |
| 0.7.0 | 1 / 41 | |
| 0.6.0 | 1 / 41 | |
| 0.5.1 | 1 / 41 | |
| 0.5.0 | 1 / 41 | |
| 0.4.1 | 1 / 41 | |
| 0.4.0 | 1 / 41 | |
| 0.3.0 | 1 / 41 | |
| 0.2.0 | 1 / 41 | |
| 0.1.67 | 1 / 41 | |
| 0.1.66 | 1 / 41 | |
| 0.1.65 | 1 / 41 | |
| 0.1.64 | 1 / 41 | |
| 0.1.63 | 1 / 41 | |
| 0.1.62 | 1 / 41 | |
| 0.1.61 | 1 / 41 | |
| 0.1.60 | 1 / 41 | |
| 0.1.59 | 1 / 41 | |
| 0.1.58 | 1 / 41 | |
| 0.1.57 | 1 / 41 | |
| 0.1.56 | 1 / 41 | |
| 0.1.55 | 1 / 41 | |
| 0.1.54 | 1 / 41 | |
| 0.1.53 | 1 / 41 | |
| 0.1.52 | 1 / 41 | |
| 0.1.51 | 1 / 41 | |
| 0.1.50 | 1 / 41 | |
| 0.1.49 | 1 / 41 | |
| 0.1.48 | 1 / 41 | |
| 0.1.47 | 1 / 41 | |
| 0.1.46 | 1 / 41 | |
| 0.1.45 | 1 / 41 | |
| 0.1.44 | 1 / 41 | |
| 0.1.43 | 1 / 41 | |
| 0.1.42 | 1 / 41 | |
| 0.1.41 | 1 / 41 | |
| 0.1.40 | 1 / 41 | |
| 0.1.39 | 1 / 41 | |
| 0.1.38 | 1 / 41 | |
| 0.1.37 | 1 / 41 | |
| 0.1.36 | 1 / 41 | |
| 0.1.35 | 1 / 41 | |
| 0.1.34 | 1 / 41 | |
| 0.1.33 | 1 / 41 | |
| 0.1.32 | 1 / 41 | |
| 0.1.31 | 1 / 41 | |
| 0.1.30 | 1 / 41 | |
| 0.1.29 | 1 / 41 | |
| 0.1.28 | 1 / 41 | |
| 0.1.27 | 1 / 41 |
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.