updated 2026-10-11 08:08 UTC

Developer Kit

Repository

Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI.

Agent Skills Python Listed MIT

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

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 10%
Last push 31d ago
Compare Developer Kit

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Developer Kit scores 46.1/100 (Grade D), ranked #286 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 5.0/10; 10% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Developer Kit 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 Developer Kit 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/giuseppe-trisciuoglio/developer-kit, MIT, last pushed 2026-09-10. 10% 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 5.0/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. Developer Kit 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-09-03 OSSF Scorecard: 5.2/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 Developer Kit’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 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 Developer Kit compares in Agent Skills

  1. #284 Super Agent Party 46.3 +0.2
  2. #285 Skill Based Architecture 46.2 +0.1
  3. #286 Developer Kit 46.1 this agent
  4. #287 Claude Skills Marketplace 46.1 ±0
  5. #288 Fable Method 46.0 −0.1

Bars show each HVTrust score; the tick marks Developer Kit’s 46.1.

Where the 46.1 comes from

HVTrust dimensions vs the Agent Skills average

46.1 / 100 · 100.0% confidence

Developer Kit Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
1.0 below 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.8 / 17
0.7 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
9.9 / 20
4.2 below avg 14.1
AdoptionLog-scaled stars · package downloads
6.1 / 20
2.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-10-10
Rank Moved
Rank dropped 26 spots (#256 → #282)
2026-10-10
Activity Score Changed
Activity score down 6pts (50 → 44)
2026-10-08
Rank Moved
Rank dropped 11 spots (#249 → #260)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
Refresh maintenance signals The repo was last pushed 31 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Developer Kit View Agent Skills Report missing data
43.6
Activity sub-score · out of 100
#286
In Agent Skills

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 →

Signals refreshed 2026-10-11 08:08 UTC · Repo last pushed 31 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
357
Forks
41
Last Push
2026-09-10
31 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
16
Rank Change
▼4
was #282

Analysis

Activity Inputs

43.6 / 100
StarsRepository reach
15.3 / 30
FreshnessLast push recency
20.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.5 / 20

Common questions about Developer Kit

Public trust evidence for Developer Kit 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 Developer Kit publish package provenance?
No published build provenance is currently detected for Developer Kit. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Developer Kit have an OpenSSF Scorecard?
Developer Kit has an OpenSSF Scorecard score of 5.0/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 Developer Kit actively maintained?
Slowing down. Last push was 31 days ago — keep an eye on whether activity resumes.
What license does Developer Kit use?
Developer Kit ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Developer Kit's commits signed?
10% of the last 100 commits to Developer Kit 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
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 Developer Kit'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 dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain Developer Kit?

For maintainers

HVTrust scores Developer Kit 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 6HVTrust 3Listed 2Score 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-10
Rank Moved
Rank dropped 26 spots (#256 → #282)
2026-10-10
Activity Score Changed
Activity score down 6pts (50 → 44)
2026-10-08
Rank Moved
Rank dropped 11 spots (#249 → #260)
2026-09-25
Rank Moved
Rank rose 81 spots (#326 → #245)
2026-09-25
HVTrust Changed
HVTrust up 16.6pts (33.0 → 49.6)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank dropped 35 spots (#292 → #327)
2026-09-23
HVTrust Changed
HVTrust up 5.7pts (27.3 → 33.0)
2026-09-22
Newly Listed
First tracked at rank #292
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 10 spots (#306 → #316)
2026-09-10
Activity Score Changed
Activity score up 6pts (52 → 58)
2026-09-03
Scorecard Added
OSSF Scorecard: 5.2/10
2026-09-03
Rank Moved
Rank rose 56 spots (#321 → #265)
2026-09-03
HVTrust Changed
HVTrust up 17.6pts (15.4 → 33.0)
2026-08-26
Newly Listed
First tracked at rank #300
GitHub →

Embed Badge Badge guide for maintainers →

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