Is Claude Seo safe to use?

Claude Seo has an HVTrust score of 14.5/100 (Grade D), ranked #254 of 331 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude Seo?

Claude Seo scores 14.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 15.3k GitHub stars and is categorized under Agent Skills.

Claude Seo

AgriciDaniel/claude-seo

Pending first signal refresh

Agent Skills Python Grade D Listed

14.5/100

Rank #254 of 331

Compare Claude Seo

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-26 · 0d ago

Recent change

New

Is Claude Seo safe? Claude Seo scores 14.5/100 (Grade D), ranked #254 of 331 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-26. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#252 Claude Code Rails Upgrade Skill — 14.5 (D) → #253 Ios Simulator Skill — 14.5 (D) → #255 Claude Code Skill Factory — 14.4 (D) → #256 AI company — 14.4 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-26

Newly Listed

First tracked at rank #254

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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 Seo View Agent Skills Report missing data

76.2

Activity sub-score · out of 100

#254

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

15.3k

Forks

2.3k

Last Push

2026-08-26

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

HVTrust Dimensions vs Agent Skills

14.5 / 100 · 40.0% confidence

Claude Seo Agent Skills average (331 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

0 / 25

1.7 below avg 1.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.1

Transparency50% declared license · 50% OSSF Scorecard

0 / 17

4.4 below avg 4.4

Maintenance60% last-push freshness · 40% commit activity

15.4 / 20

0.9 above avg 14.5

AdoptionLog-scaled stars · package downloads

10.0 / 20

1.7 above avg 8.3

Activity Inputs

76.2 / 100

StarsRepository reach

25.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

15.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

—

Unable to query

Is Claude Seo safe?

Public trust evidence for Claude Seo 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 Claude Seo publish package provenance?

No published build provenance is currently detected for Claude Seo. 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 Seo have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Claude Seo. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Claude Seo actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Claude Seo use?

Claude Seo ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 Claude Seo?

For maintainers

HVTrust scores Claude Seo 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

2026-08-26

Newly Listed

First tracked at rank #254

GitHub → PyPI: claude-seo

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/claude-seo.svg)](https://hvtracker.net/agents/claude-seo)
            
HTML:
            <a href="https://hvtracker.net/agents/claude-seo"><img src="https://hvtracker.net/badge/claude-seo.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON