Is OpenViking safe?
OpenViking scores 47.1/100 (Grade D), ranked #298 of 417 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
no OSSF Scorecard result yet;
100% of recent commits are signed;
last pushed 2026-07-14. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
47.1/100 · Grade D
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
12.5/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-14
Newly Listed
First tracked at rank #298
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-15 01:00 UTC·Repo last pushed yesterday
Public trust evidence for OpenViking is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does OpenViking publish package provenance?
Yes. OpenViking's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OpenViking have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for OpenViking. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is OpenViking actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenViking use?
OpenViking ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenViking's commits signed?
100% of the last 100 commits to OpenViking are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
MCP Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
search
shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain OpenViking?
HVTrust scores OpenViking from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
