@langchain/openai
OpenAI integrations for LangChain.js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Alpha pre-release with restructured build pipeline; missing gitHead is a process artifact, not a supply chain indicator. Package metadata and repo URL are consistent with the official LangChain org. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version restructuring (0.6.9 → 1.0.0-alpha.1) naturally introduces many new source files; new large files are source maps, expected build artifacts. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a standard monorepo placeholder version for the LangChain.js workspace; not indicative of malicious intent for this well-established package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from human (hntrl) to GitHub Actions CI/CD with SLSA provenance — a deliberate supply chain security improvement for the langchain-ai org, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (andy-langchain, rcasup) are LangChain org members; addition is consistent with normal team growth at an active organization. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of nfcampos alongside CI/CD migration is consistent with legitimate maintainer roster changes at the langchain-ai org. | ai |
Versions (showing 61 of 161)
v1.3.0-dev-1773962633795
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773786580575
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773785150055
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773776071697
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773712098100
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773710628974
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773709997654
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0-dev-1773698445534
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.13-dev-1773345797648
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.8-dev-1771365493298
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3-dev-1768440391024
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0-dev-1765433794876
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0-dev-1765432861398
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0-dev-1765431816670
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0-alpha.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hntrl.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0-alpha.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hntrl.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0-alpha.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hntrl.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.