GoLive
Website
Take your agent-built product live: hosting, database, domain, email, payments — on your own accounts. Open-source Agent Skill + zero-dependency Node CLI: detect → plan → approve → apply → verify. No GoLive account, backend or telemetry.
Is GoLive safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare GoLive
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: GoLive scores 31.8/100 (Grade D), ranked #383 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 67% of recent commits are signed; no published advisory affects its latest release (golive); last pushed 2026-10-11. Every point is earned from checkable signals — never paid placement. How scoring works →
How GoLive 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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +32.9 → 64.7 C · #71 of 396
- Publish build provenance for its packagesnpm publish --provenance from CI +28.8 → 60.6 C · #110 of 396
- Sign every commit67% signed today +1.1 → 32.9 D · #380 of 396
Chain of custody
Scanners check what the code says. This traces who ships GoLive 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.
-
Source Partly signed
github.com/mikehasa/golive-skill, MIT, last pushed 2026-10-11. 67% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages Linked, not attested
- npm golive Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: golive 0.1.0-alpha.9. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of GoLive.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues GoLive’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 GoLive compares in Agent Skills
- #381 Auto Commenter 32.4 +0.6
- #382 Bundles Forge 32.3 +0.5
- #383 GoLive 31.8 this agent
- #384 Claude to IM skill 31.7 −0.1
- #385 Founder Skills 31.6 −0.2
Bars show each HVTrust score; the tick marks GoLive’s 31.8.
Where the 31.8 comes from
HVTrust dimensions vs the Agent Skills average
31.8 / 100 · 67.0% confidenceGoLive Agent Skills average (396 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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 →
Activity & Reach
Analysis
Activity Inputs
49.0 / 100Common questions about GoLive
Does GoLive publish package provenance?
Does GoLive have an OpenSSF Scorecard?
Is GoLive actively maintained?
What license does GoLive use?
Are GoLive's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain GoLive?
For maintainers
HVTrust scores GoLive 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/golive)
<a href="https://hvtracker.net/agents/golive"><img src="https://hvtracker.net/badge/golive.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON