@langchain/textsplitters
Various implementations of LangChain.js text splitters
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): hntrl is a known LangChain org contributor with strong track record; package.json still references official langchain-ai GitHub org. Legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (eric_langchain, hntrl, christian-bromann) are consistent with LangChain org team rotation; package metadata still points to official repo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of vbarda and sullivan-sean is consistent with an org-level maintainer rotation, not a hostile takeover. Official repo URL unchanged. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the established initial version pattern for @langchain/* monorepo packages published by the official LangChain team; not indicative of malicious intent. | ai | |
| dependencies | unvetted-dep:js-tiktoken | AI (dependencies): js-tiktoken is a standard tokenizer library expected in LangChain text splitting packages; stable legitimate dependency for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 1 / 11 | |
| 1.0.0 | 1 / 11 | |
| 0.1.0 | 1 / 23 | |
| 0.0.3 | 2 / 22 | |
| 0.0.2 | 2 / 22 | |
| 0.0.1 | 2 / 22 | |
| 0.0.0 | 2 / 22 |
v1.0.1
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.