← Home

@langchain/anthropic

npm Repository Homepage
42
Versions
—
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 learningmlanthropicembeddingsvectorstores

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainers (andy-langchain, rcasup) are part of the LangChain organization; normal team evolution. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal of nfcampos is normal team change within the LangChain org, not a takeover signal. ai
provenance slsa-provenance AI (provenance): SLSA provenance attestation confirms legitimate CI/CD publishing pipeline. ai
provenance publisher-changed AI (provenance): Publisher changed from human account to GitHub Actions CI/CD with SLSA provenance attestation. This is the expected pattern for langchain packages. ai

Versions (showing 42 of 42)

Version Deps Published
1.4.0 2 / 12
1.3.29 2 / 12
1.3.28 2 / 12
1.3.27 2 / 13
1.3.26 2 / 16
1.3.25 2 / 16
1.3.24 2 / 16
1.3.23 2 / 16
1.3.22 2 / 16
1.3.21 2 / 16
1.3.20 2 / 16
1.3.19 2 / 16
1.3.18 2 / 16
1.3.17 2 / 16
1.3.16 2 / 16
1.3.15 2 / 16
1.3.14 2 / 16
1.3.13 2 / 16
1.3.12 2 / 16
1.3.11 2 / 16
1.3.10 2 / 16
1.3.8 2 / 16
1.3.7 2 / 16
1.3.6 2 / 16
1.3.5 2 / 16
1.3.4 2 / 16
1.3.3 2 / 16
1.3.2 2 / 16
1.3.1 2 / 16
1.3.0 2 / 16
1.2.3 2 / 15
1.2.2 2 / 15
1.2.1 2 / 15
1.2.0 2 / 15
1.1.3 1 / 16
1.1.2 1 / 16
1.1.1 1 / 16
1.1.0 1 / 16
1.0.1 1 / 16
1.0.0 1 / 14
0.3.34 2 / 23
0.3.33 2 / 23

v1.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.29

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.28

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.27

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.7

2 findings
HIGH Publisher changed: hntrl → GitHub Actions (on 2026-01-08) provenance

This version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.3

2 findings
HIGH Publisher changed: hntrl → GitHub Actions (on 2025-12-05) provenance

This version was published by a different npm account than previous versions on 2025-12-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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

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