Terrashark

Terraform Skill for Claude Code and Codex. LLMs hallucinate a lot with Terraform - TerraShark fixes this. It eliminates hallucinations, is designed for modular and secure code and grounds your IaC in the official Hashicorp Terraform best practices.

Agent Skills Listed MIT

Is Terrashark safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 46%
Last push 8d ago
Compare Terrashark
Suggest a correction

In detail: Terrashark scores 52.7/100 (Grade C), ranked #204 of 371 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 4.2/10; 46% of recent commits are signed; last pushed 2026-10-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Terrashark 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 Terrashark 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/LukasNiessen/terrashark, MIT, last pushed 2026-10-02. 46% 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 4.2/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 1
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages None

    No registry package. Terrashark 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-08-29 OSSF Scorecard: 3.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Terrashark’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 Terrashark compares in Agent Skills

  1. #202 Claude Code Skills Zh 52.7 ±0
  2. #203 Baoyu Design 52.7 ±0
  3. #204 Terrashark 52.7 this agent
  4. #205 TourMind Booking Skills 52.7 ±0
  5. #206 Claude Code Guide 52.7 ±0

Bars show each HVTrust score; the tick marks Terrashark’s 52.7.

Where the 52.7 comes from

HVTrust dimensions vs the Agent Skills average

52.7 / 100 · 100.0% confidence

Terrashark Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.6 / 25
in line with 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.1 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
15.6 / 20
1.5 above avg 14.1
AdoptionLog-scaled stars · package downloads
6.9 / 20
2.1 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-10-03
Rank Moved
Rank dropped 20 spots (#175 → #195)
2026-10-02
Rank Moved
Rank rose 18 spots (#193 → #175)
2026-10-01
Rank Moved
Rank dropped 10 spots (#183 → #193)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
60.7
Activity sub-score · out of 100
#204

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-10-10 20:07 UTC · Repo last pushed 8 days ago

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
715
Forks
27
Last Push
2026-10-02
8 days ago
Commits (4 wk)
10
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #204

Analysis

Activity Inputs

60.7 / 100
StarsRepository reach
17.1 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
13.0 / 25
CommunityFork signal
6.7 / 20

Common questions about Terrashark

Public trust evidence for Terrashark is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Terrashark publish package provenance?
No published build provenance is currently detected for Terrashark. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Terrashark have an OpenSSF Scorecard?
Terrashark has an OpenSSF Scorecard score of 4.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 Terrashark actively maintained?
Maintained. Last push was 8 days ago.
What license does Terrashark use?
Terrashark ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Terrashark's commits signed?
46% of the last 100 commits to Terrashark 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
low 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
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 Terrashark'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
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain Terrashark?

For maintainers

HVTrust scores Terrashark 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 15Listed 2HVTrust 2Grade 2Scorecard 1Score 1Delisted 1MCP 1Surface 1
2026-10-03
Rank Moved
Rank dropped 20 spots (#175 → #195)
2026-10-02
Rank Moved
Rank rose 18 spots (#193 → #175)
2026-10-01
Rank Moved
Rank dropped 10 spots (#183 → #193)
2026-09-25
Rank Moved
Rank dropped 17 spots (#164 → #181)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 59 spots (#104 → #163)
2026-09-23
HVTrust Changed
HVTrust up 10.5pts (43.4 → 53.9)
2026-09-22
Newly Listed
First tracked at rank #104
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 22 spots (#186 → #164)
2026-09-18
Rank Moved
Rank rose 12 spots (#198 → #186)
2026-09-14
Grade Changed
Trust grade D → C
2026-09-14
Rank Moved
Rank rose 33 spots (#228 → #195)
2026-09-13
Rank Moved
Rank rose 17 spots (#245 → #228)
2026-09-13
Activity Score Changed
Activity score up 12pts (49 → 60)
2026-09-05
Rank Moved
Rank dropped 13 spots (#189 → #202)
2026-09-01
Rank Moved
Rank dropped 14 spots (#155 → #169)
2026-08-31
Rank Moved
Rank dropped 18 spots (#137 → #155)
2026-08-30
Rank Moved
Rank dropped 24 spots (#113 → #137)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-29
Rank Moved
Rank rose 147 spots (#260 → #113)
2026-08-29
HVTrust Changed
HVTrust up 27.9pts (19.7 → 47.6)
2026-08-28
Rank Moved
Rank dropped 10 spots (#250 → #260)
2026-08-26
Newly Listed
First tracked at rank #247

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/terrashark.svg)](https://hvtracker.net/agents/terrashark)
HTML:
<a href="https://hvtracker.net/agents/terrashark"><img src="https://hvtracker.net/badge/terrashark.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