@langchain/openai MIT 42 versions

@langchain/openai

npm Repository Homepage

OpenAI integrations for LangChain.js

42

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hwchase17jacoblee93basprouleric_langchainandrewnguonlydavidduongmaddyadamssam_noyeslangchain-securityandy-langchainrcasuphntrlchristian-bromann

Keywords

llmaigpt3chainpromptprompt engineeringchatgptmachine learningmlopenaiembeddingsvectorstores

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	2026/04/23
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	2026/04/23
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	2026/04/22
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	2026/04/22
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	2026/04/22
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	2026/04/22

Versions (showing 42 of 142)

Show 17 prereleases

Version	Deps	Published
0.2.2	5 / 21	2024-07-16
0.2.1	5 / 21	2024-06-27
0.2.0	5 / 21	2024-06-21
0.1.3	5 / 21	2024-06-12
0.1.2	5 / 20	2024-06-06
0.1.1	5 / 19	2024-06-01
0.1.0	5 / 19	2024-05-31
0.0.34	5 / 19	2024-05-28
0.0.33	5 / 19	2024-05-19
0.0.32	5 / 19	2024-05-17
0.0.31	5 / 19	2024-05-15
0.0.30	5 / 19	2024-05-15
0.0.29	5 / 19	2024-05-14
0.0.28	5 / 18	2024-04-11
0.0.27	5 / 18	2024-04-10
0.0.26	5 / 18	2024-04-04
0.0.25	5 / 18	2024-03-29
0.0.24	5 / 18	2024-03-27
0.0.23	5 / 18	2024-03-22
0.0.22	5 / 18	2024-03-19
0.0.21	5 / 18	2024-03-15
0.0.20	5 / 18	2024-03-14
0.0.19	5 / 18	2024-03-10
0.0.18	5 / 18	2024-03-07
0.0.17	5 / 18	2024-03-07
0.0.16	5 / 18	2024-03-05
0.0.15	5 / 18	2024-02-27
0.0.14	5 / 18	2024-02-01
0.0.13	5 / 17	2024-01-26
0.0.12	5 / 17	2024-01-15
0.0.11	5 / 17	2024-01-11
0.0.10	5 / 17	2024-01-06
0.0.9	5 / 17	2023-12-29
0.0.8	5 / 17	2023-12-23
0.0.7	5 / 17	2023-12-20
0.0.6	5 / 17	2023-12-17
0.0.5	5 / 17	2023-12-12
0.0.4	5 / 17	2023-12-12
0.0.3	5 / 17	2023-12-12
0.0.2	5 / 17	2023-12-11
0.0.1	4 / 17	2023-11-23
0.0.0	4 / 17	2023-11-23

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.