updated 2026-10-11 08:08 UTC

Claude Blog

Repository Website by AgriciDaniel

Claude Code blog skill suite: 30 sub-skills, 5 agents, 5-gate v1.9.0 Blog Delivery Contract, dual-optimized for Google rankings and AI citations. Active development at AI-Marketing-Hub/claude-blog (AI Marketing Hub Pro community); public releases ship here.

Agent Skills Python Listed MIT

Is Claude Blog safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.1 / 10
Provenance None
Signed commits 49%
Last push 2d ago
Compare Claude Blog

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Claude Blog scores 56.7/100 (Grade C), ranked #141 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 6.1/10; 49% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Blog 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 Claude Blog 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/AgriciDaniel/claude-blog, MIT, last pushed 2026-10-09. 49% 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 6.1/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. Claude Blog 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-27 OSSF Scorecard: 6.1/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 Claude Blog’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 Claude Blog compares in Agent Skills

  1. #139 Secondsky Claude Skills 56.8 +0.1
  2. #140 Han 56.8 +0.1
  3. #141 Claude Blog 56.7 this agent
  4. #142 Claude Code My Workflow 56.7 ±0
  5. #143 Goose Skills 56.7 ±0

Bars show each HVTrust score; the tick marks Claude Blog’s 56.7.

Where the 56.7 comes from

HVTrust dimensions vs the Agent Skills average

56.7 / 100 · 100.0% confidence

Claude Blog Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.1 / 25
2.3 above 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
13.7 / 17
1.6 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
12.8 / 20
1.3 below avg 14.1
AdoptionLog-scaled stars · package downloads
8.1 / 20
0.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-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 169 spots (#306 → #137)
2026-09-25
HVTrust Changed
HVTrust up 18.5pts (38.3 → 56.8)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/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.
Compare with another agent Get email alerts for Claude Blog View Agent Skills Report missing data
63.0
Activity sub-score · out of 100
#141
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 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-11 08:08 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
2.4k
Forks
401
Last Push
2026-10-09
2 days ago
Commits (4 wk)
2?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #140

Analysis

Activity Inputs

63.0 / 100
StarsRepository reach
20.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
12.1 / 20

Common questions about Claude Blog

Claude Blog 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 Claude Blog publish package provenance?
No published build provenance is currently detected for Claude Blog. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Claude Blog have an OpenSSF Scorecard?
Claude Blog has an OpenSSF Scorecard score of 6.1/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 Claude Blog actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Claude Blog use?
Claude Blog ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Blog's commits signed?
49% of the last 100 commits to Claude Blog 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
Implemented
Claude Blog appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 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 Claude Blog'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 dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Claude Blog?

For maintainers

HVTrust scores Claude Blog 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 14HVTrust 3Listed 2Score 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1Grade 1
2026-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 169 spots (#306 → #137)
2026-09-25
HVTrust Changed
HVTrust up 18.5pts (38.3 → 56.8)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 42 spots (#264 → #306)
2026-09-23
HVTrust Changed
HVTrust up 7.4pts (31.1 → 38.5)
2026-09-22
Newly Listed
First tracked at rank #264
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-10
Rank Moved
Rank dropped 10 spots (#279 → #289)
2026-09-05
Rank Moved
Rank dropped 11 spots (#247 → #258)
2026-09-03
Rank Moved
Rank dropped 12 spots (#230 → #242)
2026-09-02
Rank Moved
Rank dropped 12 spots (#218 → #230)
2026-09-01
Rank Moved
Rank dropped 13 spots (#205 → #218)
2026-08-31
Rank Moved
Rank dropped 16 spots (#189 → #205)
2026-08-30
Rank Moved
Rank dropped 32 spots (#157 → #189)
2026-08-29
Rank Moved
Rank dropped 38 spots (#119 → #157)
2026-08-28
Rank Moved
Rank dropped 24 spots (#95 → #119)
2026-08-27
Scorecard Added
OSSF Scorecard: 6.1/10
2026-08-27
Rank Moved
Rank rose 187 spots (#282 → #95)
2026-08-27
HVTrust Changed
HVTrust up 20.8pts (17.5 → 38.3)
2026-08-26
Rank Moved
Rank dropped 141 spots (#141 → #282)
2026-08-25
Activity Score Changed
Activity score up 12pts (52 → 64)
2026-08-22
Activity Score Changed
Activity score down 11pts (62 → 52)
2026-08-16
Rank Moved
Rank dropped 11 spots (#131 → #142)
2026-08-11
Newly Listed
First tracked at rank #130
GitHub → Website →

Embed Badge Badge guide for maintainers →

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