updated 2026-11-15 04:07 UTC

DevSpace

Repository Website

Minimal Coding Agent Harness on MCP for ChatGPT, Claude, Hermes, Grok Bot, OpenClaw

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.5 / 10
Provenance Attested
Signed commits 20%
Last push 14d ago
Advisories None known
Compare DevSpace

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: DevSpace scores 78.2/100 (Grade B), ranked #225 of 1387 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 3.5/10; 20% of recent commits are signed; no published advisory affects its latest release (@waishnav/devspace); last pushed 2026-11-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How DevSpace 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 DevSpace 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 Partly signed

    github.com/Waishnav/devspace, MIT, last pushed 2026-11-01. 20% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @waishnav/devspace 1.1.1. No published advisory affects it (OSV, checked 2026-11-15).

Changes to this chain

  • 2026-10-31 Package provenance attestation detected
  • 2026-10-14 OSSF Scorecard: 4.7/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 DevSpace’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 DevSpace compares in MCP Servers

  1. #127 XcodeBuildMCP 78.3 +0.1
  2. #128 Universal Screenshot MCP 78.3 +0.1
  3. #129 DevSpace 78.2 this agent
  4. #130 BLS OEWS 78.1 −0.1
  5. #131 FHIR MCP Server 78.0 −0.2

Bars show each HVTrust score; the tick marks DevSpace’s 78.2.

Where the 78.2 comes from

HVTrust dimensions vs the MCP Servers average

78.2 / 100 · 100.0% confidence

DevSpace MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.9 / 25
2.0 above avg 10.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
6.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
12.7 / 20
5.1 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-06
Rank Moved
Rank dropped 12 spots (#187 → #199)
2026-11-02
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-11-02
Grade Changed
Trust grade A → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
83.6
Activity sub-score · out of 100
#129
In MCP Servers

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-11-15 04:07 UTC · Repo last pushed 14 days ago

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
5.5k
Forks
624
Last Push
2026-11-01
14 days ago
Commits (4 wk)
402
Downloads (7d)
603
npm
HN mentions (30d)
—
Open Issues
20
Rank Change
=
was #225

Analysis

Activity Inputs

83.6 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.0 / 20

Common questions about DevSpace

Public supply-chain signals for DevSpace are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but DevSpace carries less obvious unverified-evidence risk than projects with thin signals.
Does DevSpace publish package provenance?
Yes. DevSpace's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does DevSpace have an OpenSSF Scorecard?
DevSpace has an OpenSSF Scorecard score of 3.5/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 DevSpace actively maintained?
Maintained. Last push was 14 days ago.
What license does DevSpace use?
DevSpace ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DevSpace's commits signed?
20% of the last 100 commits to DevSpace 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
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
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 DevSpace'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-11-02
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-10-31
Provenance Added
Package provenance attestation detected

Maintain DevSpace?

For maintainers

HVTrust scores DevSpace 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 16HVTrust 4Grade 3Score 2Listed 1Scorecard 1Provenance 1MCP 1
2026-11-06
Rank Moved
Rank dropped 12 spots (#187 → #199)
2026-11-02
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-11-02
Grade Changed
Trust grade A → B
2026-11-02
Rank Moved
Rank dropped 42 spots (#137 → #179)
2026-10-31
Provenance Added
Package provenance attestation detected
2026-10-31
Grade Changed
Trust grade C → A
2026-10-31
Rank Moved
Rank rose 480 spots (#619 → #139)
2026-10-31
HVTrust Changed
HVTrust up 19.2pts (62.5 → 81.7)
2026-10-30
Rank Moved
Rank rose 12 spots (#631 → #619)
2026-10-29
Rank Moved
Rank dropped 73 spots (#558 → #631)
2026-10-28
Rank Moved
Rank dropped 26 spots (#532 → #558)
2026-10-27
Rank Moved
Rank rose 122 spots (#654 → #532)
2026-10-27
HVTrust Changed
HVTrust up 3.3pts (61.3 → 64.6)
2026-10-26
Rank Moved
Rank rose 169 spots (#823 → #654)
2026-10-26
HVTrust Changed
HVTrust up 5.7pts (55.6 → 61.3)
2026-10-26
Activity Score Changed
Activity score up 27pts (58 → 85)
2026-10-19
Rank Moved
Rank dropped 41 spots (#767 → #808)
2026-10-18
Rank Moved
Rank dropped 16 spots (#751 → #767)
2026-10-15
Rank Moved
Rank dropped 36 spots (#707 → #743)
2026-10-15
Activity Score Changed
Activity score down 5pts (71 → 66)
2026-10-14
Scorecard Added
OSSF Scorecard: 4.7/10
2026-10-14
Grade Changed
Trust grade D → C
2026-10-14
Rank Moved
Rank rose 599 spots (#1306 → #707)
2026-10-14
HVTrust Changed
HVTrust up 25.5pts (33.1 → 58.6)
2026-10-10
Rank Moved
Rank dropped 28 spots (#1267 → #1295)
2026-10-09
Rank Moved
Rank dropped 16 spots (#1251 → #1267)
2026-10-08
Rank Moved
Rank dropped 10 spots (#1241 → #1251)
2026-10-07
Rank Moved
Rank dropped 12 spots (#1229 → #1241)
2026-09-29
Newly Listed
First tracked at rank #1213
GitHub → Website → npm: @waishnav/devspace

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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