@apify/consts
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 2.54.2 | 0 / 0 | |
| 2.54.1 | 0 / 0 | |
| 2.54.0 | 0 / 0 | |
| 2.53.3 | 0 / 0 | |
| 2.53.2 | 0 / 0 | |
| 2.53.1 | 0 / 0 | |
| 2.53.0 | 0 / 0 | |
| 2.52.2 | 0 / 0 | |
| 2.52.1 | 0 / 0 | |
| 2.52.0 | 0 / 0 | |
| 2.51.1 | 0 / 0 | |
| 2.51.0 | 0 / 0 | |
| 2.50.0 | 0 / 0 | |
| 2.49.0 | 0 / 0 | |
| 2.48.1 | 0 / 0 | |
| 2.48.0 | 0 / 0 | |
| 2.47.1 | 0 / 0 | |
| 2.47.0 | 0 / 0 | |
| 2.46.0 | 0 / 0 | |
| 2.45.0 | 0 / 0 | |
| 2.44.1 | 0 / 0 | |
| 2.44.0 | 0 / 0 | |
| 2.43.0 | 0 / 0 | |
| 2.42.0 | 0 / 0 | |
| 2.41.0 | 0 / 0 | |
| 2.40.0 | 0 / 0 | |
| 2.39.0 | 0 / 0 | |
| 2.38.0 | 0 / 0 | |
| 2.37.0 | 0 / 0 | |
| 2.36.0 | 0 / 0 | |
| 2.35.0 | 0 / 0 | |
| 2.34.0 | 0 / 0 | |
| 2.33.0 | 0 / 0 | |
| 2.32.0 | 0 / 0 | |
| 2.31.0 | 0 / 0 | |
| 2.30.0 | 0 / 0 | |
| 2.29.0 | 0 / 0 | |
| 2.28.1 | 0 / 0 | |
| 2.28.0 | 0 / 0 | |
| 2.27.0 | 0 / 0 | |
| 2.26.0 | 0 / 0 | |
| 2.25.1 | 0 / 0 | |
| 2.25.0 | 0 / 0 | |
| 2.24.0 | 0 / 0 | |
| 2.23.0 | 0 / 0 | |
| 2.22.0 | 0 / 0 | |
| 2.21.0 | 0 / 0 | |
| 2.20.0 | 0 / 0 | |
| 2.19.0 | 0 / 0 | |
| 2.18.0 | 0 / 0 | |
| 2.17.0 | 0 / 0 |
v2.54.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.54.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.54.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.