@apify/input_schema
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 9 of 109)
| Version | Deps | Published |
|---|---|---|
| 3.8.0 | 3 / 0 | |
| 3.7.1 | 3 / 0 | |
| 3.7.0 | 3 / 0 | |
| 3.6.3 | 3 / 0 | |
| 3.6.2 | 3 / 0 | |
| 3.6.1 | 3 / 0 | |
| 3.6.0 | 3 / 0 | |
| 3.5.17 | 3 / 0 | |
| 3.5.16 | 3 / 0 |
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.