@effect-app/infra
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cross-fetch | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:path-parser | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:query-string | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval used in codeFilter query engine to evaluate generated filter expressions; not user-controlled supply-chain risk. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard Basic Auth header decoding in middleware; not a payload-hiding pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in CUPS printing module for legitimate subprocess invocation; stable pattern for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.10.0 | 10 / 19 | |
| 3.9.0 | 10 / 19 | |
| 3.8.1 | 10 / 19 | |
| 3.8.0 | 10 / 19 | |
| 3.7.3 | 10 / 19 | |
| 3.7.2 | 10 / 19 | |
| 3.7.1 | 10 / 19 | |
| 3.7.0 | 10 / 19 | |
| 3.6.2 | 10 / 19 |
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.