@grackle-ai/knowledge-core
Generic knowledge graph SDK on top of Neo4j with vector search, graph traversal, and pluggable embedders/chunkers
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 10 of 228)
| Version | Deps | Published |
|---|---|---|
| 0.68.2 | 3 / 4 | |
| 0.68.1 | 3 / 4 | |
| 0.68.0 | 3 / 4 | |
| 0.67.0 | 3 / 4 | |
| 0.66.0 | 3 / 4 | |
| 0.65.0 | 3 / 4 | |
| 0.64.2 | 3 / 4 | |
| 0.64.1 | 3 / 4 | |
| 0.64.0 | 3 / 4 | |
| 0.63.0 | 3 / 4 |
v0.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.