@php-wasm/web-5-2
PHP 5.2 WebAssembly binaries for web (legacy)
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in Emscripten-generated WASM asyncify glue code (ASM_CONSTS pattern); stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ini | AI (phantom-deps): ini is a runtime dep used in config handling; phantom-dep heuristic misfires for this package. | ai | |
| phantom-deps | phantom-dep:@php-wasm/universal | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic misfires for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.1.36 | 2 / 0 | |
| 3.1.35 | 2 / 0 | |
| 3.1.34 | 2 / 0 | |
| 3.1.33 | 2 / 0 | |
| 3.1.32 | 2 / 0 | |
| 3.1.31 | 2 / 0 | |
| 3.1.30 | 2 / 0 | |
| 3.1.29 | 2 / 0 | |
| 3.1.28 | 4 / 0 | |
| 3.1.27 | 4 / 0 | |
| 3.1.26 | 4 / 0 | |
| 3.1.25 | 3 / 0 | |
| 3.1.22 | 3 / 0 | |
| 3.1.21 | 3 / 0 | |
| 3.1.20 | 3 / 0 |
v3.1.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.