@donmahallem/renovate-config
General renovate config
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 51 of 103)
| Version | Deps | Published |
|---|---|---|
| 0.15.47 | 0 / 1 | |
| 0.15.46 | 0 / 1 | |
| 0.15.45 | 0 / 1 | |
| 0.15.44 | 0 / 1 | |
| 0.15.43 | 0 / 1 | |
| 0.15.42 | 0 / 1 | |
| 0.15.41 | 0 / 1 | |
| 0.15.40 | 0 / 1 | |
| 0.15.39 | 0 / 1 | |
| 0.15.38 | 0 / 1 | |
| 0.15.37 | 0 / 1 | |
| 0.15.36 | 0 / 1 | |
| 0.15.35 | 0 / 1 | |
| 0.15.34 | 0 / 1 | |
| 0.15.33 | 0 / 1 | |
| 0.15.32 | 0 / 1 | |
| 0.15.31 | 0 / 1 | |
| 0.15.30 | 0 / 1 | |
| 0.15.29 | 0 / 1 | |
| 0.15.28 | 0 / 1 | |
| 0.15.27 | 0 / 1 | |
| 0.15.3 | 0 / 1 | |
| 0.15.2 | 0 / 1 | |
| 0.15.1 | 0 / 1 | |
| 0.15.0 | 0 / 1 | |
| 0.13.9 | 0 / 1 | |
| 0.13.8 | 0 / 1 | |
| 0.13.7 | 0 / 1 | |
| 0.13.5 | 0 / 1 | |
| 0.13.4 | 0 / 1 | |
| 0.13.3 | 0 / 1 | |
| 0.13.2 | 0 / 1 | |
| 0.12.10 | 0 / 1 | |
| 0.12.9 | 0 / 1 | |
| 0.12.8 | 0 / 1 | |
| 0.12.7 | 0 / 1 | |
| 0.12.6 | 0 / 1 | |
| 0.12.5 | 0 / 1 | |
| 0.12.4 | 0 / 1 | |
| 0.12.3 | 0 / 1 | |
| 0.12.2 | 0 / 1 | |
| 0.12.1 | 0 / 1 | |
| 0.12.0 | 0 / 1 | |
| 0.11.0 | 0 / 1 | |
| 0.10.10 | 0 / 1 | |
| 0.10.9 | 0 / 1 | |
| 0.10.8 | 0 / 1 | |
| 0.10.7 | 0 / 1 | |
| 0.10.2 | 0 / 1 | |
| 0.10.1 | 0 / 1 | |
| 0.10.0 | 0 / 1 |
v0.15.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
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.