effect-app
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established package with 819 days history and 620 versions; metadata quality issues are consistent across versions, not malicious. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Persistent metadata omission across all versions; not a malice indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance has been consistently absent; not a disqualifier for this established package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep used via config/re-export patterns; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-pattern | AI (phantom-deps): ts-pattern is a declared runtime dep; phantom-dep heuristic misfires on re-export style packages. | ai | |
| phantom-deps | phantom-dep:@tsconfig/strictest | AI (phantom-deps): TypeScript config-only dep; not imported in source, expected pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.16.0 | 10 / 8 | |
| 3.15.1 | 10 / 8 | |
| 3.14.2 | 10 / 8 | |
| 3.14.1 | 10 / 8 | |
| 3.14.0 | 10 / 8 | |
| 3.13.0 | 10 / 8 |
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.