@elizaos/plugin-ollama
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Ollama plugin legitimately installs the Ollama runtime via postinstall; consistent with package purpose. | ai | |
| phantom-deps | phantom-dep:tsup | AI (phantom-deps): tsup is a build tool used in scripts/config, not a runtime import; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:js-tiktoken | AI (phantom-deps): Used indirectly via ai-sdk dependencies; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/ui-utils | AI (phantom-deps): Transitive/config-level dependency; stable FP for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.2.4 | 6 / 3 | |
| 1.2.3 | 6 / 3 | |
| 1.2.2 | 6 / 3 | |
| 1.2.1 | 6 / 3 | |
| 1.0.8 | 6 / 3 | |
| 1.0.7 | 6 / 3 | |
| 1.0.6 | 6 / 3 | |
| 1.0.5 | 6 / 3 | |
| 1.0.4 | 6 / 2 | |
| 1.0.3 | 6 / 2 | |
| 1.0.2 | 6 / 2 | |
| 1.0.1 | 6 / 2 | |
| 1.0.0 | 6 / 2 |
v1.2.4
2 findingsScript: bun scripts/install-ollama.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
2 findingsScript: bun scripts/install-ollama.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
2 findingsScript: bun scripts/install-ollama.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsScript: bun scripts/install-ollama.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.