Is OpenViking safe to use?

OpenViking has an HVTrust score of 55.7/100 (Grade C), ranked #384 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenViking?

OpenViking scores 55.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 28.1k GitHub stars and is categorized under Memory & Knowledge.

OpenViking

volcengine/OpenViking

Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.

Memory & Knowledge Python Grade C Listed AGPL-3.0

55.7/100

Rank #384 of 1204

Compare OpenViking

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-08 · 1d ago

Recent change

Rank +3

Is OpenViking safe? OpenViking scores 55.7/100 (Grade C), ranked #384 of 1204 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; OSSF Scorecard rates its supply-chain practices 6.2/10; 100% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#26 MemOS — 59.2 (C) → #27 pgvector — 58.5 (C) → #29 Letta — 55.4 (C) → #30 LLM Wiki Agent — 51.1 (C) →

Quick Trust Read

What Would Improve It

Expose more independent signals, such as package metadata, provenance, or public usage evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 94 spots (#288 → #382)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for OpenViking View Memory & Knowledge Report missing data

92.2

Activity sub-score · out of 100

#28

In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →

Activity & Reach

Stars

28.1k

Forks

2.2k

Last Push

2026-08-08

yesterday

Commits (4 wk)

256

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

144

Rank Change

▼2

was #382

Analysis

HVTrust Dimensions vs Memory & Knowledge

55.7 / 100 · 67.0% confidence

OpenViking Memory & Knowledge average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.2 / 25

9.6 above avg 10.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.7 above avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.1 above avg 12.7

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

2.4 above avg 17.5

AdoptionLog-scaled stars · package downloads

10.7 / 20

3.4 below avg 14.1

Activity Inputs

92.2 / 100

StarsRepository reach

26.7 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.6 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 5

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 7

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is OpenViking safe?

OpenViking has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

OpenViking has an OpenSSF Scorecard score of 6.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

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.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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.

External Service Dependencies

high confidence

6 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared 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

How this surface has changed

Detected changes to OpenViking's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Google Gemini, Multi-provider (LiteLLM)

Maintain OpenViking?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 94 spots (#288 → #382)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Google Gemini, Multi-provider (LiteLLM)

2026-07-15

Scorecard Added

OSSF Scorecard: 6.3/10

2026-07-15

Grade Changed

Trust grade D → C

2026-07-15

Rank Moved

Rank rose 42 spots (#298 → #256)

2026-07-15

HVTrust Changed

HVTrust up 8.9pts (47.2 → 56.1)

2026-07-14

Newly Listed

First tracked at rank #298

GitHub → PyPI: openviking

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/openviking.svg)](https://hvtracker.net/agents/openviking)
            
HTML:
            <a href="https://hvtracker.net/agents/openviking"><img src="https://hvtracker.net/badge/openviking.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON