@dxos/effect
Effect utils.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dxos-bot → GitHub Actions is a CI/CD migration; SLSA attestation confirms official repo origin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-level CI migration; SLSA provenance confirms legitimate dxos/dxos pipeline. | ai | |
| provenance | no-provenance | AI (provenance): DXOS monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 8 / 10 | |
| 0.9.0 | 8 / 10 | |
| 0.8.3 | 4 / 2 | |
| 0.8.2 | 4 / 2 | |
| 0.8.1 | 4 / 2 | |
| 0.8.0 | 3 / 3 | |
| 0.7.4 | 3 / 3 | |
| 0.7.3 | 3 / 3 | |
| 0.7.2 | 3 / 3 | |
| 0.7.1 | 3 / 2 | |
| 0.7.0 | 3 / 2 |
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.