updated 2026-10-10 20:07 UTC

Voyager

Repository Website

Enhancement suite for Gemini, AI Studio, Claude, ChatGPT & DeepSeek — plus a prompt manager for any website, DeepSeek Harness included. / 面向 Gemini、AI Studio、Claude、ChatGPT 与 DeepSeek 的增强套件；其中的提示词管理器可用于任意网站，如 DeepSeek Harness。

Agent Skills TypeScript Listed GPL-3.0

Is Voyager safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.2 / 10
Provenance None
Signed commits 5%
Last push today
Compare Voyager

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Voyager scores 65.0/100 (Grade B), ranked #57 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.2/10; 5% of recent commits are signed; last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Voyager 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 Voyager and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/voyager-crew/voyager, GPL-3.0, last pushed 2026-10-10. 5% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions7
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 8
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 7
    Vulnerabilities 0

  3. Published packages None

    No registry package. Voyager is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-10-01 Provenance drift warning cleared (now: not_applicable)
  • 2026-09-23 Package-provenance drift warning: package metadata no longer clearly points at this repo
  • 2026-09-04 OSSF Scorecard: 5.3/10

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 Voyager’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Voyager compares in Agent Skills

  1. #55 Llmfit 65.3 +0.3
  2. #56 Claude Octopus 65.2 +0.2
  3. #57 Voyager 65.0 this agent
  4. #58 Lobehub 64.9 −0.1
  5. #59 Nanoclaw 64.4 −0.6

Bars show each HVTrust score; the tick marks Voyager’s 65.0.

Where the 65.0 comes from

HVTrust dimensions vs the Agent Skills average

65.0 / 100 · 100.0% confidence

Voyager Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
1.0 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.9 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
14.8 / 20
5.8 above avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-10
Grade Changed
Trust grade C → B
2026-10-09
Grade Changed
Trust grade B → C
2026-10-01
Drift Warning Cleared
Provenance drift warning cleared (now: not_applicable)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Voyager View Agent Skills Report missing data
89.1
Activity sub-score · out of 100
#57
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-10 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
20.3k
Forks
683
Last Push
2026-10-10
today
Commits (4 wk)
913
Downloads (7d)
2,112
npm
HN mentions (30d)
—
Open Issues
14
Rank Change
=
was #57

Analysis

Activity Inputs

89.1 / 100
StarsRepository reach
25.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.2 / 20

Common questions about Voyager

Voyager 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 Voyager publish package provenance?
No published build provenance is currently detected for Voyager. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Voyager have an OpenSSF Scorecard?
Voyager has an OpenSSF Scorecard score of 5.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 Voyager actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Voyager use?
Voyager ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Voyager's commits signed?
5% of the last 100 commits to Voyager 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Voyager'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-10-01
Drift Warning Cleared
Provenance drift warning cleared (now: not_applicable)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain Voyager?

For maintainers

HVTrust scores Voyager 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 7Grade 5HVTrust 4Listed 2Scorecard 1Delisted 1Drift 1Surface 1Drift 1
2026-10-10
Grade Changed
Trust grade C → B
2026-10-09
Grade Changed
Trust grade B → C
2026-10-01
Drift Warning Cleared
Provenance drift warning cleared (now: not_applicable)
2026-10-01
Grade Changed
Trust grade C → B
2026-10-01
Rank Moved
Rank rose 42 spots (#93 → #51)
2026-10-01
HVTrust Changed
HVTrust up 5.1pts (60.9 → 66.0)
2026-09-25
Rank Moved
Rank dropped 12 spots (#79 → #91)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 126 spots (#205 → #79)
2026-09-23
HVTrust Changed
HVTrust up 27.1pts (34.7 → 61.8)
2026-09-22
Newly Listed
First tracked at rank #205
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Grade Changed
Trust grade D → C
2026-09-11
Rank Moved
Rank rose 224 spots (#298 → #74)
2026-09-11
HVTrust Changed
HVTrust up 25.6pts (36.1 → 61.7)
2026-09-10
Rank Moved
Rank dropped 10 spots (#288 → #298)
2026-09-05
Rank Moved
Rank dropped 10 spots (#262 → #272)
2026-09-04
Scorecard Added
OSSF Scorecard: 5.3/10
2026-09-04
Rank Moved
Rank rose 60 spots (#322 → #262)
2026-09-04
HVTrust Changed
HVTrust up 20.8pts (14.8 → 35.6)
2026-08-26
Newly Listed
First tracked at rank #306
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/voyager.svg)](https://hvtracker.net/agents/voyager)
HTML:
<a href="https://hvtracker.net/agents/voyager"><img src="https://hvtracker.net/badge/voyager.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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