@langchain/langgraph-sdk MIT 62 versions

@langchain/langgraph-sdk

npm Repository Homepage

Client library for interacting with the LangGraph API

62

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_noyesandy-langchainrcasuphntrlchristian-bromann

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): @types/json-schema is a well-known DefinitelyTyped package with no malicious history; benign addition for JSON Schema type support.	ai	2026/04/22
source-diff	net-exec-file:dist/ui/stream/agent.d.cts	AI (source-diff): TypeScript declaration file (.d.cts) — contains only type definitions and JSDoc examples. Not executed at runtime. The eval() reference is inside a documentation example snippet, not live code.	ai	2026/04/22
source-diff	net-exec-file:dist/ui/stream/agent.d.ts	AI (source-diff): TypeScript declaration file (.d.ts) — contains only type definitions and JSDoc examples. Not executed at runtime. The eval() reference is inside a documentation example snippet, not live code.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): Transition from human publisher (davidduong) to GitHub Actions CI/CD is a legitimate automation upgrade for the langchain-ai org, backed by SLSA provenance attestation. Generalizes to future versions.	ai	2026/04/22
provenance	missing-githead	AI (provenance): Package has SLSA provenance attestation via Sigstore, which is a stronger integrity signal than gitHead. Published by GitHub Actions from the official langchain-ai org.	ai	2026/04/22
dependencies	unvetted-dep:p-retry	AI (dependencies): p-retry is a well-known sindresorhus utility with no security concerns; stable false positive for this package.	ai	2026/04/21
phantom-deps	phantom-dep:@types/json-schema	AI (phantom-deps): @types/json-schema is used as a type-only dependency in this TypeScript SDK; declaring it as a runtime dep for type re-exports is a known pattern. Stable false positive for this package.	ai	2026/04/21

Versions (showing 62 of 162)

Version	Deps	Published
0.0.65	4 / 18	2025-04-09
0.0.64	4 / 18	2025-04-08
0.0.63	4 / 18	2025-04-08
0.0.62	4 / 18	2025-03-28
0.0.61	4 / 18	2025-03-28
0.0.60	4 / 18	2025-03-19
0.0.59	4 / 18	2025-03-19
0.0.57	4 / 18	2025-03-13
0.0.56	4 / 18	2025-03-13
0.0.54	4 / 18	2025-03-13
0.0.53	4 / 18	2025-03-11
0.0.52	4 / 18	2025-03-10
0.0.51	4 / 18	2025-03-10
0.0.50	4 / 18	2025-03-07
0.0.49	4 / 18	2025-03-06
0.0.48	4 / 18	2025-03-06
0.0.47	4 / 18	2025-03-06
0.0.46	4 / 16	2025-03-05
0.0.45	4 / 16	2025-02-20
0.0.44	4 / 16	2025-02-20
0.0.43	4 / 16	2025-02-19
0.0.42	4 / 16	2025-02-14
0.0.41	4 / 16	2025-02-13
0.0.40	4 / 16	2025-02-13
0.0.39	4 / 16	2025-02-12
0.0.38	4 / 13	2025-02-11
0.0.37	4 / 13	2025-02-07
0.0.36	4 / 13	2025-01-10
0.0.35	4 / 9	2025-01-10
0.0.34	4 / 9	2025-01-08
0.0.33	4 / 9	2025-01-01
0.0.32	4 / 9	2024-12-10
0.0.31	4 / 9	2024-12-04
0.0.30	4 / 9	2024-12-03
0.0.29	4 / 9	2024-11-27
0.0.28	4 / 9	2024-11-26
0.0.27	4 / 9	2024-11-26
0.0.26	4 / 9	2024-11-19
0.0.25	4 / 9	2024-11-15
0.0.24	4 / 9	2024-11-15
0.0.23	4 / 9	2024-11-11
0.0.22	4 / 8	2024-11-06
0.0.21	4 / 8	2024-11-04
0.0.20	4 / 8	2024-10-30
0.0.19	4 / 8	2024-10-28
0.0.18	4 / 8	2024-10-25
0.0.17	4 / 8	2024-10-16
0.0.16	4 / 8	2024-10-07
0.0.15	4 / 8	2024-10-04
0.0.14	4 / 8	2024-10-01
0.0.13	4 / 8	2024-09-29
0.0.11	4 / 8	2024-09-24
0.0.10	4 / 8	2024-09-17
0.0.9	5 / 8	2024-09-11
0.0.8	5 / 8	2024-08-27
0.0.7	5 / 8	2024-08-24
0.0.6	5 / 8	2024-08-23
0.0.5	5 / 8	2024-08-21
0.0.4	5 / 8	2024-08-06
0.0.3	5 / 8	2024-08-01
0.0.2	5 / 8	2024-07-16
0.0.1	5 / 8	2024-07-03

v0.0.65

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.64

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.63

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.62

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.61

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.60

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.59

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.57

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.56

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.54

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.53

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.52

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.51

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.50

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.49

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.48

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.47

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.46

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.45

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.44

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.43

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.42

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.41

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.40

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.39

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.38

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.37

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.36

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.35

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.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.