@apify/log
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @apify package; not a typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @apify package; not a typosquat of got. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @apify package; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @apify package; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @apify package; not a typosquat of zod. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @apify package; not a typosquat of glob. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.5.39 | 2 / 0 | |
| 2.5.38 | 2 / 0 | |
| 2.5.37 | 2 / 0 | |
| 2.5.36 | 2 / 0 | |
| 2.5.35 | 2 / 0 | |
| 2.5.34 | 2 / 0 | |
| 2.5.33 | 2 / 0 | |
| 2.5.32 | 2 / 0 | |
| 2.5.31 | 2 / 0 | |
| 2.5.30 | 2 / 0 | |
| 2.5.29 | 2 / 0 | |
| 2.5.28 | 2 / 0 | |
| 2.5.27 | 2 / 0 | |
| 2.5.26 | 2 / 0 | |
| 2.5.25 | 2 / 0 | |
| 2.5.24 | 2 / 0 | |
| 2.5.23 | 2 / 0 | |
| 2.5.22 | 2 / 0 | |
| 2.5.21 | 2 / 0 | |
| 2.5.20 | 2 / 0 | |
| 2.5.19 | 2 / 0 | |
| 2.5.18 | 2 / 0 |
v2.5.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.