@arizeai/openinference-instrumentation-langchain
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 | no-provenance | AI (provenance): Established Arize-ai org package; absence of Sigstore provenance is common and not a risk for this publisher. | ai | |
| dependencies | unvetted-dep:@arizeai/openinference-core | AI (dependencies): Same publisher org (Arize AI); internal dependency within the openinference monorepo, stable across versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 5 / 16 | |
| 4.0.11 | 5 / 16 | |
| 4.0.10 | 5 / 16 | |
| 4.0.9 | 5 / 16 | |
| 4.0.8 | 5 / 16 | |
| 4.0.7 | 5 / 16 | |
| 4.0.6 | 5 / 16 | |
| 4.0.1 | 5 / 16 | |
| 4.0.0 | 5 / 16 |
v4.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.