updated 2026-10-13 04:10 UTC

OpenViking

Repository Website

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

Memory & Knowledge Python Listed AGPL-3.0

Is OpenViking safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.4 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare OpenViking

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

Pick any agent to compare →
Suggest a correction

In detail: OpenViking scores 88.3/100 (Grade A), ranked #38 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.4/10; 100% of recent commits are signed; no published advisory affects its latest release (openviking); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenViking could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenViking and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/volcengine/OpenViking, AGPL-3.0, last pushed 2026-10-13. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.4/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 9
    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 1
    SAST 7
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI openviking Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: openviking 0.5.0. No published advisory affects it (OSV, checked 2026-10-12).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of OpenViking.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues OpenViking’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How OpenViking compares in Memory & Knowledge

  1. #1 OpenViking 88.3 this agent
  2. #2 ReMe 87.8 −0.5
  3. #3 EverOS 87.4 −0.9
  4. #4 Graphiti 87.1 −1.2
  5. #5 LanceDB 86.7 −1.6

Bars show each HVTrust score; the tick marks OpenViking’s 88.3.

Where the 88.3 comes from

HVTrust dimensions vs the Memory & Knowledge average

88.3 / 100 · 100.0% confidence

OpenViking Memory & Knowledge average (49 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.5 / 25
8.8 above avg 11.7
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.4 above avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.0 above avg 12.9
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.7 above avg 17.3
AdoptionLog-scaled stars · package downloads
17.8 / 20
4.6 above avg 13.2

Quick Trust Read

What Would Improve It
Improve transparency to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/10. Tighten the weakest checks to improve public safety evidence.
Compare with ReMe Get email alerts for OpenViking View Memory & Knowledge Report missing data
93.9
Activity sub-score · out of 100
#1
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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
39.8k
Forks
3.2k
Last Push
2026-10-13
today
Commits (4 wk)
422
Downloads (7d)
113,300
pypi
HN mentions (30d)
—
Open Issues
289
Rank Change
▲1
was #39

Analysis

Activity Inputs

93.9 / 100
StarsRepository reach
27.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.3 / 20

Common questions about OpenViking

Public supply-chain signals for OpenViking are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OpenViking carries less obvious unverified-evidence risk than projects with thin signals.
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.4/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.

Compare OpenViking head-to-head

OpenViking vs ReMe → OpenViking vs EverOS → OpenViking vs Graphiti →

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
8 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-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: Firecrawl

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
Rank 15Surface 2HVTrust 1Grade 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: Firecrawl
2026-09-03
Grade Changed
Trust grade C → A
2026-09-03
Rank Moved
Rank rose 504 spots (#531 → #27)
2026-09-03
HVTrust Changed
HVTrust up 31.8pts (56.1 → 87.9)
2026-09-02
Rank Moved
Rank dropped 12 spots (#519 → #531)
2026-09-01
Rank Moved
Rank dropped 31 spots (#488 → #519)
2026-08-31
Rank Moved
Rank dropped 28 spots (#460 → #488)
2026-08-30
Rank Moved
Rank rose 12 spots (#472 → #460)
2026-08-29
Rank Moved
Rank dropped 16 spots (#456 → #472)
2026-08-27
Rank Moved
Rank dropped 10 spots (#438 → #448)
2026-08-26
Rank Moved
Rank dropped 38 spots (#400 → #438)
2026-08-24
Rank Moved
Rank dropped 18 spots (#379 → #397)
2026-08-22
Rank Moved
Rank rose 19 spots (#400 → #381)
2026-08-19
Rank Moved
Rank dropped 16 spots (#382 → #398)
2026-08-17
Rank Moved
Rank rose 15 spots (#399 → #384)
2026-08-12
Rank Moved
Rank rose 16 spots (#402 → #386)
2026-08-10
Rank Moved
Rank dropped 18 spots (#384 → #402)
2026-08-08
Rank Moved
Rank dropped 94 spots (#288 → #382)
GitHub → Website → PyPI: openviking

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 88.3 Grade A
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.4 · Raw JSON