@php-wasm/logger
A logger for PHP-wasm clients like Playground and WP-now.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fs-ext | AI (phantom-deps): fs-ext is declared as an optionalDependency; phantom-dep false positive for this package. | ai |
Versions (showing 82 of 82)
| Version | Deps | Published |
|---|---|---|
| 3.1.47 | 0 / 0 | |
| 3.1.46 | 0 / 0 | |
| 3.1.45 | 0 / 0 | |
| 3.1.44 | 0 / 0 | |
| 3.1.43 | 0 / 0 | |
| 3.1.42 | 0 / 0 | |
| 3.1.41 | 0 / 0 | |
| 3.1.40 | 0 / 0 | |
| 3.1.39 | 0 / 0 | |
| 3.1.38 | 0 / 0 | |
| 3.1.36 | 0 / 0 | |
| 3.1.35 | 0 / 0 | |
| 3.1.34 | 0 / 0 | |
| 3.1.33 | 0 / 0 | |
| 3.1.32 | 0 / 0 | |
| 3.1.31 | 0 / 0 | |
| 3.1.30 | 0 / 0 | |
| 3.1.29 | 0 / 0 | |
| 3.1.28 | 0 / 0 | |
| 3.1.27 | 0 / 0 | |
| 3.1.26 | 0 / 0 | |
| 3.1.25 | 0 / 0 | |
| 3.1.22 | 0 / 0 | |
| 3.1.21 | 0 / 0 | |
| 3.1.20 | 0 / 0 | |
| 3.1.19 | 1 / 0 | |
| 3.1.18 | 1 / 0 | |
| 3.1.16 | 1 / 0 | |
| 3.1.15 | 1 / 0 | |
| 3.1.14 | 1 / 0 | |
| 3.1.13 | 1 / 0 | |
| 3.1.12 | 1 / 0 | |
| 3.1.11 | 1 / 0 | |
| 3.1.10 | 1 / 0 | |
| 3.1.9 | 1 / 0 | |
| 3.1.8 | 1 / 0 | |
| 3.1.5 | 1 / 0 | |
| 3.1.4 | 1 / 0 | |
| 3.1.3 | 1 / 0 | |
| 3.1.2 | 1 / 0 | |
| 3.1.1 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 3.0.54 | 1 / 0 | |
| 3.0.53 | 1 / 0 | |
| 3.0.52 | 1 / 0 | |
| 3.0.51 | 1 / 0 | |
| 3.0.46 | 1 / 0 | |
| 3.0.45 | 1 / 0 | |
| 3.0.44 | 1 / 0 | |
| 3.0.43 | 1 / 0 | |
| 3.0.42 | 1 / 0 | |
| 3.0.41 | 1 / 0 | |
| 3.0.40 | 1 / 0 | |
| 3.0.39 | 1 / 0 | |
| 3.0.38 | 1 / 0 | |
| 3.0.37 | 1 / 0 | |
| 3.0.36 | 1 / 0 | |
| 3.0.35 | 1 / 0 | |
| 3.0.34 | 1 / 0 | |
| 3.0.33 | 1 / 0 | |
| 3.0.32 | 1 / 0 | |
| 3.0.31 | 1 / 0 | |
| 3.0.30 | 1 / 0 | |
| 3.0.22 | 2 / 0 | |
| 3.0.21 | 2 / 0 | |
| 3.0.20 | 2 / 0 | |
| 3.0.19 | 2 / 0 | |
| 3.0.18 | 2 / 0 | |
| 3.0.17 | 2 / 0 | |
| 3.0.16 | 2 / 0 | |
| 3.0.15 | 2 / 0 | |
| 3.0.14 | 2 / 0 | |
| 3.0.13 | 2 / 0 | |
| 3.0.12 | 2 / 0 | |
| 3.0.8 | 2 / 0 | |
| 3.0.6 | 2 / 0 | |
| 3.0.5 | 2 / 0 | |
| 3.0.4 | 2 / 0 | |
| 3.0.3 | 2 / 0 | |
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 |
v3.1.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.30
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (adamziel) on 2025-12-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.