@effect/ai-openai
Effect modules for working with AI apis
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): Effect-TS monorepo switched to GitHub Actions CI publishing; SLSA attestation confirms official repo origin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects the monorepo release cadence, not account takeover; SLSA provenance corroborates legitimacy. | ai |
Versions (showing 51 of 196)
| Version | Deps | Published |
|---|---|---|
| 0.41.0 | 1 / 0 | |
| 0.40.2 | 1 / 0 | |
| 0.40.1 | 1 / 0 | |
| 0.40.0 | 1 / 0 | |
| 0.39.2 | 1 / 0 | |
| 0.39.1 | 1 / 0 | |
| 0.39.0 | 1 / 0 | |
| 0.38.0 | 1 / 0 | |
| 0.37.2 | 1 / 0 | |
| 0.37.1 | 1 / 0 | |
| 0.37.0 | 1 / 0 | |
| 0.36.0 | 1 / 0 | |
| 0.35.0 | 1 / 0 | |
| 0.34.0 | 1 / 0 | |
| 0.33.0 | 1 / 0 | |
| 0.32.1 | 1 / 0 | |
| 0.32.0 | 1 / 0 | |
| 0.31.1 | 1 / 0 | |
| 0.31.0 | 1 / 0 | |
| 0.30.2 | 1 / 0 | |
| 0.30.1 | 1 / 0 | |
| 0.30.0 | 1 / 0 | |
| 0.29.1 | 1 / 0 | |
| 0.29.0 | 1 / 0 | |
| 0.28.2 | 1 / 0 | |
| 0.28.1 | 1 / 0 | |
| 0.28.0 | 1 / 0 | |
| 0.27.0 | 1 / 0 | |
| 0.26.1 | 1 / 0 | |
| 0.26.0 | 1 / 0 | |
| 0.25.3 | 1 / 0 | |
| 0.25.2 | 1 / 0 | |
| 0.25.1 | 1 / 0 | |
| 0.25.0 | 1 / 0 | |
| 0.24.17 | 1 / 0 | |
| 0.24.16 | 1 / 0 | |
| 0.24.15 | 1 / 0 | |
| 0.24.14 | 1 / 0 | |
| 0.24.13 | 1 / 0 | |
| 0.24.12 | 1 / 0 | |
| 0.24.11 | 1 / 0 | |
| 0.24.10 | 1 / 0 | |
| 0.24.9 | 1 / 0 | |
| 0.24.8 | 1 / 0 | |
| 0.24.7 | 1 / 0 | |
| 0.24.6 | 1 / 0 | |
| 0.24.5 | 1 / 0 | |
| 0.24.4 | 1 / 0 | |
| 0.24.3 | 1 / 0 | |
| 0.24.2 | 1 / 0 | |
| 0.24.1 | 1 / 0 |
v0.41.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.40.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.37.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.37.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.37.0
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 (michael.arnaldi) on 2025-12-18, 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.
v0.36.0
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 (michael.arnaldi) on 2025-12-01, 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.