OpenViking

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

Memory & Knowledge Python Grade C Listed AGPL-3.0
56.6/100
Rank #460 of 1316
Compare OpenViking

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-29 · 0d ago
Recent change
Rank +3

Is OpenViking safe? OpenViking scores 56.6/100 (Grade C), ranked #460 of 1316 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.7/10; 100% of recent commits are signed; last pushed 2026-08-29. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

Quick Trust Read

What Would Improve It
Expose more independent signals, such as package metadata, provenance, or public usage evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.7/10. Tighten the weakest checks to improve public safety evidence.
93.1
Activity sub-score · out of 100
#31

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 →

Signals refreshed 2026-08-29 03:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-29

Activity & Reach

Stars
34.2k
Forks
2.6k
Last Push
2026-08-29
today
Commits (4 wk)
309
Downloads (7d)
HN mentions (30d)
Open Issues
190
Rank Change
▼4
was #456

Analysis

HVTrust Dimensions vs Memory & Knowledge

56.6 / 100 · 67.0% confidence

OpenViking Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.9 / 25
10.7 above avg 10.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.7 above avg 12.3
Transparency50% declared license · 50% OSSF Scorecard
14.2 / 17
1.7 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.6 above avg 17.4
AdoptionLog-scaled stars · package downloads
10.9 / 20
2.7 below avg 13.6

Activity Inputs

93.1 / 100
StarsRepository reach
27.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.9 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.7 / 10
OpenSSF Scorecard · scanned Aug 27, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
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 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.7/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

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.

Reputation Timeline

Signal history
Rank 10Listed 1HVTrust 1Grade 1Scorecard 1
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)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.6 Grade C
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.3 · Raw JSON