@nsshunt/stsconfig
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
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 1.27.71 | 3 / 8 | |
| 1.27.70 | 3 / 8 | |
| 1.27.69 | 3 / 8 | |
| 1.27.68 | 3 / 8 | |
| 1.27.67 | 3 / 8 | |
| 1.27.66 | 3 / 8 | |
| 1.27.65 | 3 / 8 | |
| 1.27.64 | 3 / 8 | |
| 1.27.63 | 3 / 8 | |
| 1.27.62 | 3 / 8 | |
| 1.27.61 | 3 / 8 | |
| 1.27.60 | 3 / 8 | |
| 1.27.59 | 3 / 8 | |
| 1.27.58 | 3 / 8 | |
| 1.27.57 | 3 / 8 | |
| 1.27.56 | 3 / 8 | |
| 1.27.55 | 3 / 8 | |
| 1.27.54 | 3 / 9 | |
| 1.27.53 | 3 / 9 | |
| 1.27.51 | 3 / 9 | |
| 1.27.49 | 3 / 9 | |
| 1.27.48 | 3 / 9 | |
| 1.27.47 | 3 / 9 | |
| 1.27.46 | 3 / 9 | |
| 1.27.45 | 3 / 9 | |
| 1.27.44 | 3 / 9 | |
| 1.27.43 | 3 / 9 | |
| 1.27.42 | 3 / 9 | |
| 1.27.41 | 3 / 9 | |
| 1.27.40 | 3 / 9 | |
| 1.27.39 | 3 / 9 | |
| 1.27.38 | 3 / 9 | |
| 1.27.37 | 3 / 9 | |
| 1.27.36 | 3 / 9 | |
| 1.27.35 | 3 / 9 | |
| 1.27.34 | 3 / 9 | |
| 1.27.33 | 3 / 9 | |
| 1.27.32 | 3 / 9 | |
| 1.27.31 | 3 / 9 | |
| 1.27.30 | 3 / 9 | |
| 1.27.29 | 3 / 9 | |
| 1.27.28 | 3 / 9 | |
| 1.27.27 | 3 / 9 | |
| 1.27.26 | 3 / 9 | |
| 1.27.25 | 3 / 9 | |
| 1.27.24 | 3 / 9 | |
| 1.27.23 | 3 / 9 | |
| 1.27.22 | 3 / 9 | |
| 1.27.21 | 3 / 9 | |
| 1.27.20 | 3 / 9 | |
| 1.27.19 | 3 / 9 | |
| 1.27.18 | 3 / 9 | |
| 1.27.17 | 3 / 9 | |
| 1.27.16 | 3 / 9 | |
| 1.27.15 | 3 / 9 | |
| 1.27.14 | 3 / 9 | |
| 1.27.13 | 3 / 9 | |
| 1.27.12 | 3 / 9 | |
| 1.27.11 | 3 / 9 | |
| 1.27.10 | 3 / 9 | |
| 1.27.9 | 3 / 9 | |
| 1.27.8 | 3 / 9 | |
| 1.27.7 | 3 / 9 |
v1.27.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.