@grackle-ai/plugin-knowledge
Knowledge graph plugin for Grackle — Neo4j, embeddings, and knowledge MCP tools
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 127)
| Version | Deps | Published |
|---|---|---|
| 0.106.1 | 10 / 4 | |
| 0.106.0 | 10 / 4 | |
| 0.105.0 | 10 / 4 | |
| 0.104.0 | 10 / 4 | |
| 0.103.0 | 10 / 4 | |
| 0.102.0 | 10 / 4 | |
| 0.101.0 | 10 / 4 | |
| 0.100.1 | 10 / 4 | |
| 0.100.0 | 10 / 4 | |
| 0.99.0 | 10 / 4 |
v0.106.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.