@apify/input_secrets
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@apify/log | AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep heuristic fires as false positive for this package. | ai |
Versions (showing 100 of 125)
| Version | Deps | Published |
|---|---|---|
| 1.2.50 | 3 / 0 | |
| 1.2.49 | 3 / 0 | |
| 1.2.48 | 3 / 0 | |
| 1.2.47 | 3 / 0 | |
| 1.2.46 | 3 / 0 | |
| 1.2.45 | 3 / 0 | |
| 1.2.43 | 3 / 0 | |
| 1.2.42 | 3 / 0 | |
| 1.2.41 | 3 / 0 | |
| 1.2.40 | 3 / 0 | |
| 1.2.39 | 3 / 0 | |
| 1.2.38 | 3 / 0 | |
| 1.2.37 | 3 / 0 | |
| 1.2.36 | 3 / 0 | |
| 1.2.35 | 3 / 0 | |
| 1.2.34 | 3 / 0 | |
| 1.2.33 | 3 / 0 | |
| 1.2.32 | 3 / 0 | |
| 1.2.31 | 3 / 0 | |
| 1.2.30 | 3 / 0 | |
| 1.2.29 | 3 / 0 | |
| 1.2.28 | 3 / 0 | |
| 1.2.27 | 3 / 0 | |
| 1.2.26 | 3 / 0 | |
| 1.2.25 | 3 / 0 | |
| 1.2.24 | 3 / 0 | |
| 1.2.23 | 3 / 0 | |
| 1.2.22 | 3 / 0 | |
| 1.2.21 | 3 / 0 | |
| 1.2.20 | 3 / 0 | |
| 1.2.19 | 3 / 0 | |
| 1.2.18 | 3 / 0 | |
| 1.2.17 | 3 / 0 | |
| 1.2.16 | 3 / 0 | |
| 1.2.15 | 3 / 0 | |
| 1.2.14 | 3 / 0 | |
| 1.2.11 | 3 / 0 | |
| 1.2.10 | 3 / 0 | |
| 1.2.9 | 3 / 0 | |
| 1.2.8 | 3 / 0 | |
| 1.2.7 | 3 / 0 | |
| 1.2.6 | 3 / 0 | |
| 1.2.5 | 3 / 0 | |
| 1.2.4 | 3 / 0 | |
| 1.2.3 | 3 / 0 | |
| 1.2.2 | 3 / 0 | |
| 1.2.1 | 3 / 0 | |
| 1.2.0 | 3 / 0 | |
| 1.1.76 | 3 / 0 | |
| 1.1.75 | 3 / 0 | |
| 1.1.74 | 3 / 0 | |
| 1.1.73 | 3 / 0 | |
| 1.1.72 | 3 / 0 | |
| 1.1.71 | 3 / 0 | |
| 1.1.70 | 3 / 0 | |
| 1.1.69 | 3 / 0 | |
| 1.1.68 | 3 / 0 | |
| 1.1.67 | 3 / 0 | |
| 1.1.66 | 3 / 0 | |
| 1.1.65 | 3 / 0 | |
| 1.1.64 | 3 / 0 | |
| 1.1.63 | 3 / 0 | |
| 1.1.62 | 3 / 0 | |
| 1.1.61 | 3 / 0 | |
| 1.1.60 | 3 / 0 | |
| 1.1.59 | 3 / 0 | |
| 1.1.58 | 3 / 0 | |
| 1.1.57 | 3 / 0 | |
| 1.1.56 | 3 / 0 | |
| 1.1.55 | 3 / 0 | |
| 1.1.54 | 3 / 0 | |
| 1.1.53 | 3 / 0 | |
| 1.1.52 | 3 / 0 | |
| 1.1.51 | 3 / 0 | |
| 1.1.50 | 3 / 0 | |
| 1.1.49 | 3 / 0 | |
| 1.1.48 | 3 / 0 | |
| 1.1.47 | 3 / 0 | |
| 1.1.46 | 3 / 0 | |
| 1.1.45 | 3 / 0 | |
| 1.1.44 | 3 / 0 | |
| 1.1.43 | 3 / 0 | |
| 1.1.42 | 3 / 0 | |
| 1.1.41 | 3 / 0 | |
| 1.1.40 | 3 / 0 | |
| 1.1.39 | 3 / 0 | |
| 1.1.38 | 3 / 0 | |
| 1.1.37 | 3 / 0 | |
| 1.1.36 | 3 / 0 | |
| 1.1.35 | 3 / 0 | |
| 1.1.34 | 3 / 0 | |
| 1.1.33 | 3 / 0 | |
| 1.1.32 | 3 / 0 | |
| 1.1.31 | 3 / 0 | |
| 1.1.30 | 3 / 0 | |
| 1.1.29 | 3 / 0 | |
| 1.1.28 | 3 / 0 | |
| 1.1.27 | 3 / 0 | |
| 1.1.26 | 3 / 0 | |
| 1.1.25 | 3 / 0 |
v1.2.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.