@langchain/langgraph-checkpoint-sqlite
LangGraph
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the intentional initial version scheme used across the LangGraph JS monorepo; not indicative of malicious throwaway package given established publisher and official repo. | ai | |
| provenance | no-provenance | AI (provenance): Publisher jacoblee93 has a long track record; lack of provenance is common and not a risk signal for this package. | ai | |
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation which supersedes gitHead as a source link. The transition to GitHub Actions CI/CD publishing explains the missing gitHead field. | ai | |
| provenance | publisher-changed | AI (provenance): LangChain migrated to GitHub Actions for automated publishing, corroborated by SLSA provenance attestation. This is a legitimate CI/CD transition for the official langchain-ai org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): andy-langchain and rcasup are LangChain organization accounts; addition is consistent with normal team evolution at an established org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): nfcampos removal is consistent with team role changes at LangChain; no evidence of hostile takeover given SLSA attestation and official repo match. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 1 / 21 | |
| 1.0.0 | 1 / 21 | |
| 0.2.1 | 1 / 22 | |
| 0.2.0 | 1 / 22 | |
| 0.1.5 | 1 / 28 | |
| 0.1.4 | 1 / 28 | |
| 0.1.3 | 1 / 28 | |
| 0.1.2 | 1 / 28 | |
| 0.1.1 | 1 / 28 | |
| 0.0.1 | 1 / 27 | |
| 0.0.0 | 1 / 27 |
v1.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-01-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.