Stagewise

The Open Source Agentic IDE. Create and orchestrate coding agents, show app previews and run git workflows. Use your fav

Coding Agents TypeScript Grade C Listed AGPL-3.0
59.0/100
Rank #398 of 1316
Compare Stagewise

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

Is Stagewise safe? Stagewise scores 59.0/100 (Grade C), ranked #398 of 1316 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.6/10; recent commits are unsigned; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-27
Rank Moved
Rank dropped 14 spots (#380 → #394)
2026-08-26
Rank Moved
Rank dropped 39 spots (#341 → #380)
2026-08-24
Rank Moved
Rank dropped 19 spots (#324 → #343)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/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.
83.5
Activity sub-score · out of 100
#32

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 12 days ago

Rank Trend

2026-08-11 2026-08-29

Activity & Reach

Stars
6.8k
Forks
507
Last Push
2026-08-17
12 days ago
Commits (4 wk)
90
Downloads (7d)
HN mentions (30d)
Open Issues
9
Rank Change
▼3
was #395

Analysis

HVTrust Dimensions vs Coding Agents

59.0 / 100 · 100.0% confidence

Stagewise Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.0 / 25
1.1 below avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.8 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
19.0 / 20
4.2 above avg 14.8
AdoptionLog-scaled stars · package downloads
9.2 / 20
3.1 below avg 12.3

Activity Inputs

83.5 / 100
StarsRepository reach
23.0 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
24.4 / 25
CommunityFork signal
12.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Aug 29, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 6
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 6
Security-Policy 4
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Stagewise safe?

Stagewise 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 Stagewise publish package provenance?
No published build provenance is currently detected for Stagewise. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Stagewise have an OpenSSF Scorecard?
Stagewise has an OpenSSF Scorecard score of 5.6/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 Stagewise actively maintained?
Maintained. Last push was 12 days ago.
What license does Stagewise use?
Stagewise ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Stagewise's commits signed?
0% of the last 100 commits to Stagewise 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
high confidence
1 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.
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

Maintain Stagewise?

For maintainers

HVTrust scores Stagewise 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 11Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-27
Rank Moved
Rank dropped 14 spots (#380 → #394)
2026-08-26
Rank Moved
Rank dropped 39 spots (#341 → #380)
2026-08-24
Rank Moved
Rank dropped 19 spots (#324 → #343)
2026-08-22
Rank Moved
Rank rose 19 spots (#339 → #320)
2026-08-19
Rank Moved
Rank dropped 13 spots (#323 → #336)
2026-08-17
Rank Moved
Rank rose 18 spots (#340 → #322)
2026-08-13
Rank Moved
Rank dropped 17 spots (#312 → #329)
2026-08-12
Rank Moved
Rank rose 17 spots (#329 → #312)
2026-08-10
Rank Moved
Rank dropped 11 spots (#317 → #328)
2026-08-08
Rank Moved
Rank dropped 77 spots (#238 → #315)
2026-07-15
Scorecard Added
OSSF Scorecard: 5.4/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 182 spots (#397 → #215)
2026-07-15
HVTrust Changed
HVTrust up 35.7pts (23.4 → 59.1)
2026-07-14
Newly Listed
First tracked at rank #397

Embed Badge Badge guide for maintainers →

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

Other agents in Coding Agents

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.3 · Raw JSON