@apify/utilities
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used for safe error property access in retry logic; not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is part of a documented crypto/decryption utility in the Apify shared lib. | ai |
Versions (showing 100 of 128)
| Version | Deps | Published |
|---|---|---|
| 2.35.1 | 2 / 1 | |
| 2.35.0 | 2 / 1 | |
| 2.34.2 | 2 / 1 | |
| 2.34.1 | 2 / 1 | |
| 2.34.0 | 2 / 1 | |
| 2.33.1 | 2 / 1 | |
| 2.32.2 | 2 / 1 | |
| 2.32.1 | 2 / 1 | |
| 2.32.0 | 2 / 1 | |
| 2.31.2 | 2 / 1 | |
| 2.31.1 | 2 / 1 | |
| 2.31.0 | 2 / 1 | |
| 2.30.0 | 2 / 1 | |
| 2.29.4 | 2 / 1 | |
| 2.29.3 | 2 / 1 | |
| 2.29.2 | 2 / 1 | |
| 2.29.1 | 2 / 1 | |
| 2.29.0 | 2 / 1 | |
| 2.28.0 | 2 / 1 | |
| 2.27.0 | 2 / 1 | |
| 2.26.1 | 2 / 1 | |
| 2.26.0 | 2 / 1 | |
| 2.25.6 | 2 / 1 | |
| 2.25.5 | 2 / 1 | |
| 2.25.4 | 2 / 1 | |
| 2.25.3 | 2 / 1 | |
| 2.25.2 | 2 / 1 | |
| 2.25.1 | 2 / 1 | |
| 2.25.0 | 2 / 1 | |
| 2.24.1 | 2 / 1 | |
| 2.24.0 | 2 / 1 | |
| 2.23.4 | 2 / 1 | |
| 2.23.3 | 2 / 1 | |
| 2.23.2 | 2 / 1 | |
| 2.23.1 | 2 / 1 | |
| 2.23.0 | 2 / 1 | |
| 2.20.3 | 2 / 1 | |
| 2.20.2 | 2 / 1 | |
| 2.20.1 | 2 / 1 | |
| 2.20.0 | 2 / 1 | |
| 2.19.1 | 2 / 1 | |
| 2.19.0 | 2 / 1 | |
| 2.18.2 | 2 / 1 | |
| 2.18.1 | 2 / 1 | |
| 2.18.0 | 2 / 1 | |
| 2.17.0 | 2 / 1 | |
| 2.16.2 | 2 / 1 | |
| 2.16.1 | 2 / 1 | |
| 2.16.0 | 2 / 1 | |
| 2.15.6 | 2 / 1 | |
| 2.15.5 | 2 / 1 | |
| 2.15.4 | 2 / 1 | |
| 2.15.3 | 2 / 1 | |
| 2.15.2 | 2 / 1 | |
| 2.15.1 | 2 / 1 | |
| 2.15.0 | 2 / 1 | |
| 2.14.0 | 2 / 1 | |
| 2.13.1 | 2 / 1 | |
| 2.13.0 | 2 / 1 | |
| 2.12.2 | 2 / 1 | |
| 2.12.1 | 2 / 1 | |
| 2.12.0 | 2 / 1 | |
| 2.11.1 | 2 / 1 | |
| 2.11.0 | 2 / 1 | |
| 2.10.11 | 2 / 1 | |
| 2.10.10 | 2 / 1 | |
| 2.10.9 | 2 / 1 | |
| 2.10.8 | 2 / 1 | |
| 2.10.7 | 2 / 1 | |
| 2.10.6 | 2 / 1 | |
| 2.10.5 | 2 / 1 | |
| 2.10.4 | 2 / 1 | |
| 2.10.3 | 2 / 1 | |
| 2.10.2 | 2 / 1 | |
| 2.10.1 | 2 / 1 | |
| 2.10.0 | 2 / 1 | |
| 2.9.9 | 2 / 1 | |
| 2.9.8 | 2 / 1 | |
| 2.9.7 | 2 / 1 | |
| 2.9.6 | 2 / 1 | |
| 2.9.5 | 2 / 1 | |
| 2.9.4 | 2 / 1 | |
| 2.9.3 | 2 / 1 | |
| 2.9.2 | 2 / 1 | |
| 2.9.1 | 2 / 1 | |
| 2.9.0 | 2 / 1 | |
| 2.8.0 | 2 / 1 | |
| 2.7.10 | 2 / 1 | |
| 2.7.9 | 2 / 1 | |
| 2.7.8 | 2 / 1 | |
| 2.7.7 | 2 / 1 | |
| 2.7.6 | 2 / 1 | |
| 2.7.5 | 2 / 1 | |
| 2.7.4 | 2 / 1 | |
| 2.7.3 | 2 / 1 | |
| 2.7.2 | 2 / 1 | |
| 2.7.1 | 2 / 1 | |
| 2.7.0 | 2 / 1 | |
| 2.6.0 | 2 / 1 | |
| 2.5.0 | 2 / 1 |
v2.35.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.34.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.