@apify/input_schema
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 100 of 109)
| Version | Deps | Published |
|---|---|---|
| 3.28.21 | 5 / 1 | |
| 3.28.20 | 5 / 1 | |
| 3.28.19 | 5 / 1 | |
| 3.28.18 | 5 / 1 | |
| 3.28.17 | 5 / 1 | |
| 3.28.16 | 5 / 1 | |
| 3.28.15 | 5 / 1 | |
| 3.28.13 | 5 / 1 | |
| 3.28.12 | 5 / 1 | |
| 3.28.11 | 5 / 1 | |
| 3.28.10 | 5 / 1 | |
| 3.28.9 | 5 / 1 | |
| 3.28.8 | 5 / 1 | |
| 3.28.7 | 5 / 1 | |
| 3.28.6 | 5 / 1 | |
| 3.28.5 | 5 / 1 | |
| 3.28.4 | 5 / 1 | |
| 3.28.3 | 5 / 1 | |
| 3.28.2 | 5 / 1 | |
| 3.28.1 | 5 / 1 | |
| 3.28.0 | 5 / 1 | |
| 3.27.7 | 5 / 1 | |
| 3.27.6 | 5 / 1 | |
| 3.27.5 | 5 / 1 | |
| 3.27.4 | 5 / 1 | |
| 3.27.3 | 5 / 1 | |
| 3.27.2 | 5 / 1 | |
| 3.27.1 | 5 / 1 | |
| 3.27.0 | 5 / 1 | |
| 3.26.0 | 5 / 1 | |
| 3.25.18 | 5 / 1 | |
| 3.25.17 | 5 / 1 | |
| 3.25.16 | 5 / 1 | |
| 3.25.15 | 5 / 1 | |
| 3.25.14 | 5 / 1 | |
| 3.25.13 | 5 / 1 | |
| 3.25.12 | 5 / 1 | |
| 3.25.11 | 5 / 1 | |
| 3.25.10 | 5 / 1 | |
| 3.25.9 | 5 / 1 | |
| 3.25.8 | 5 / 1 | |
| 3.25.7 | 5 / 1 | |
| 3.25.6 | 5 / 1 | |
| 3.25.5 | 5 / 1 | |
| 3.25.4 | 5 / 1 | |
| 3.25.3 | 5 / 1 | |
| 3.25.2 | 5 / 1 | |
| 3.25.1 | 5 / 1 | |
| 3.25.0 | 5 / 1 | |
| 3.24.0 | 5 / 1 | |
| 3.23.10 | 5 / 1 | |
| 3.23.9 | 5 / 1 | |
| 3.23.8 | 5 / 1 | |
| 3.23.5 | 5 / 1 | |
| 3.23.4 | 6 / 1 | |
| 3.23.3 | 6 / 1 | |
| 3.23.2 | 6 / 1 | |
| 3.23.1 | 6 / 1 | |
| 3.23.0 | 6 / 1 | |
| 3.22.2 | 5 / 0 | |
| 3.22.1 | 5 / 0 | |
| 3.22.0 | 5 / 0 | |
| 3.21.1 | 5 / 0 | |
| 3.21.0 | 5 / 0 | |
| 3.20.2 | 5 / 0 | |
| 3.20.1 | 5 / 0 | |
| 3.20.0 | 5 / 0 | |
| 3.19.1 | 4 / 0 | |
| 3.19.0 | 4 / 0 | |
| 3.18.4 | 4 / 0 | |
| 3.18.3 | 4 / 0 | |
| 3.18.2 | 4 / 0 | |
| 3.18.1 | 4 / 0 | |
| 3.18.0 | 4 / 0 | |
| 3.17.0 | 4 / 0 | |
| 3.16.1 | 4 / 0 | |
| 3.16.0 | 4 / 0 | |
| 3.15.2 | 3 / 0 | |
| 3.15.1 | 3 / 0 | |
| 3.15.0 | 3 / 0 | |
| 3.14.1 | 3 / 0 | |
| 3.14.0 | 3 / 0 | |
| 3.13.4 | 3 / 0 | |
| 3.13.3 | 3 / 0 | |
| 3.13.2 | 3 / 0 | |
| 3.13.1 | 3 / 0 | |
| 3.13.0 | 3 / 0 | |
| 3.12.4 | 3 / 0 | |
| 3.12.3 | 3 / 0 | |
| 3.12.2 | 3 / 0 | |
| 3.12.1 | 3 / 0 | |
| 3.12.0 | 3 / 0 | |
| 3.11.0 | 3 / 0 | |
| 3.10.0 | 3 / 0 | |
| 3.9.4 | 3 / 0 | |
| 3.9.3 | 3 / 0 | |
| 3.9.2 | 3 / 0 | |
| 3.9.1 | 3 / 0 | |
| 3.9.0 | 3 / 0 | |
| 3.8.1 | 3 / 0 |
v3.28.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.28.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.28.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.