Orchestkit

The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.

Agent Skills TypeScript Listed MIT

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

OSSF Scorecard 6.7 / 10
Provenance None
Signed commits 100%
Last push today
Advisories None known
Compare Orchestkit
Suggest a correction

In detail: Orchestkit scores 67.4/100 (Grade B), ranked #41 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 6.7/10; 100% of recent commits are signed; no published advisory affects its latest release (orchestkit); last pushed 2026-10-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Orchestkit 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.

Chain of custody

Scanners check what the code says. This traces who ships Orchestkit 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 and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/yonatangross/orchestkit, MIT, last pushed 2026-10-11. 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.7/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protectionn/a
    • Signed Releases0
    • Dangerous Workflow0
    • Token Permissions10
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 6
    SAST 9
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 9
  3. Published packages Linked, not attested

    • npm orchestkit Source link points back to this repo No build attestation
    • PyPI orchestkit No source link declared No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: orchestkit 0.1.0. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

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

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 Orchestkit’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.

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 Orchestkit compares in Agent Skills

  1. #39 Virgiliojr94 Book-to-Skill 67.7 +0.3
  2. #40 Claude Plugins Official 67.5 +0.1
  3. #41 Orchestkit 67.4 this agent
  4. #42 Thesvg 67.3 −0.1
  5. #43 nWave 67.2 −0.2

Bars show each HVTrust score; the tick marks Orchestkit’s 67.4.

Where the 67.4 comes from

HVTrust dimensions vs the Agent Skills average

67.4 / 100 · 100.0% confidence

Orchestkit Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.4 / 25
5.6 above 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
14.2 / 17
2.1 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
7.1 / 20
1.9 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.7/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.
72.0
Activity sub-score · out of 100
#41

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-11 04:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
292
Forks
35
Last Push
2026-10-11
today
Commits (4 wk)
495
Downloads (7d)
7
npm
HN mentions (30d)
—
Open Issues
112
Rank Change
▲6
was #47

Analysis

Activity Inputs

72.0 / 100
StarsRepository reach
14.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
7.2 / 20

Common questions about Orchestkit

Orchestkit 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 Orchestkit publish package provenance?
No published build provenance is currently detected for Orchestkit. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Orchestkit have an OpenSSF Scorecard?
Orchestkit 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 Orchestkit actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Orchestkit use?
Orchestkit ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Orchestkit's commits signed?
100% of the last 100 commits to Orchestkit 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
high confidence
Implemented
Orchestkit appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
medium confidence
Partial
Some package metadata matches; some source metadata is missing
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 Orchestkit'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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Orchestkit?

For maintainers

HVTrust scores Orchestkit 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
Listed 2Delisted 1HVTrust 1Rank 1Grade 1MCP 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 162 spots (#201 → #39)
2026-09-23
HVTrust Changed
HVTrust up 32.9pts (35.0 → 67.9)
2026-09-22
Newly Listed
First tracked at rank #201
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-08-26
Newly Listed
First tracked at rank #13

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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