@salesforce/code-analyzer-retirejs-engine
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 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.36.0 | 5 / 8 | |
| 0.35.0 | 5 / 8 | |
| 0.34.0 | 5 / 8 | |
| 0.33.0 | 5 / 8 | |
| 0.32.0 | 5 / 8 | |
| 0.31.0 | 5 / 8 | |
| 0.30.0 | 5 / 8 | |
| 0.29.0 | 5 / 8 | |
| 0.28.0 | 5 / 8 | |
| 0.27.0 | 5 / 8 | |
| 0.26.0 | 5 / 8 | |
| 0.25.0 | 5 / 8 | |
| 0.24.0 | 5 / 8 | |
| 0.23.0 | 5 / 8 | |
| 0.22.0 | 5 / 8 | |
| 0.21.0 | 5 / 8 | |
| 0.20.0 | 5 / 8 | |
| 0.19.0 | 5 / 8 | |
| 0.18.1 | 7 / 8 | |
| 0.18.0 | 7 / 8 | |
| 0.17.0 | 7 / 8 | |
| 0.16.2 | 7 / 8 | |
| 0.16.1 | 7 / 8 | |
| 0.15.0 | 7 / 8 | |
| 0.14.0 | 7 / 8 | |
| 0.13.0 | 7 / 8 | |
| 0.12.0 | 7 / 8 | |
| 0.11.1 | 7 / 8 | |
| 0.11.0 | 7 / 8 | |
| 0.10.0 | 7 / 8 | |
| 0.9.0 | 7 / 8 | |
| 0.8.0 | 7 / 8 | |
| 0.7.0 | 7 / 8 | |
| 0.6.0 | 7 / 8 | |
| 0.5.0 | 7 / 8 | |
| 0.2.0 | 7 / 8 | |
| 0.1.1 | 7 / 8 | |
| 0.1.0 | 7 / 8 |
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.