Is open-claude-tag safe to use?

open-claude-tag has an HVTrust score of 33.5/100 (Grade D), ranked #1308 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for open-claude-tag?

open-claude-tag scores 33.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 GitHub stars and is categorized under Voice & Conversational.

open-claude-tag

Repository by Anil-matcha

Self-hostable channel-native AI teammate for Slack. Open source alternative to Claude Tag. LLM-agnostic.

Voice & Conversational Python Listed MIT

Is open-claude-tag safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10

Provenance None

Signed commits 0%

Last push 80d ago

Compare open-claude-tag

How does it stack up against its Voice & Conversational neighbours?

Pick any agent to compare →

Suggest a correction

In detail: open-claude-tag scores 33.5/100 (Grade D), ranked #1308 of 1374 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 2.6/10; recent commits are unsigned; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How open-claude-tag 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 from 2.6 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +13.4 → 46.9 D · #12 of 13
Sign every commit0% signed today +5.0 → 38.5 D · #13 of 13

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships open-claude-tag 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.

Source Unsigned

github.com/Anil-matcha/open-claude-tag, MIT, last pushed 2026-08-17. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.6/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10
Published packages None

No registry package. open-claude-tag 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-30 OSSF Scorecard: 2.6/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 open-claude-tag’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 tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How open-claude-tag compares in Voice & Conversational

Bars show each HVTrust score; the tick marks open-claude-tag’s 33.5.

Where the 33.5 comes from

HVTrust dimensions vs the Voice & Conversational average

33.5 / 100 · 100.0% confidence

open-claude-tag Voice & Conversational average (13 agents)

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

3.2 / 25

7.7 below avg 10.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.7 below avg 12.5

Transparency50% declared license · 50% OSSF Scorecard

10.7 / 17

2.1 below avg 12.8

Maintenance60% last-push freshness · 40% commit activity

6.7 / 20

9.4 below avg 16.1

AdoptionLog-scaled stars · package downloads

3.1 / 20

7.9 below avg 11.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-09

Rank Moved

Rank dropped 10 spots (#1256 → #1266)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.6/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 80 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View Voice & Conversational Report missing data

23.1

Activity sub-score · out of 100

#13

In Voice & Conversational

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 →

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars

Forks

Last Push

2026-08-17

80 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #1308

Analysis

Activity Inputs

23.1 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

13.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

1.4 / 20

Common questions about open-claude-tag

Public trust evidence for open-claude-tag 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 open-claude-tag publish package provenance?

No published build provenance is currently detected for open-claude-tag. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does open-claude-tag have an OpenSSF Scorecard?

open-claude-tag has an OpenSSF Scorecard score of 2.6/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 open-claude-tag actively maintained?

Slowing down. Last push was 80 days ago — keep an eye on whether activity resumes.

What license does open-claude-tag use?

open-claude-tag ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are open-claude-tag's commits signed?

0% of the last 100 commits to open-claude-tag 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

open-claude-tag appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

5 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

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

How this surface has changed

Detected changes to open-claude-tag'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

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Groq, Multi-provider (LiteLLM), OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain open-claude-tag?

For maintainers

HVTrust scores open-claude-tag 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-10-09

Rank Moved

Rank dropped 10 spots (#1256 → #1266)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, Groq, Multi-provider (LiteLLM), OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 427 spots (#796 → #1223)

2026-09-23

HVTrust Changed

HVTrust up 7.4pts (28.8 → 36.2)

2026-09-22

Newly Listed

First tracked at rank #796

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank dropped 28 spots (#1182 → #1210)

2026-09-16

Activity Score Changed

Activity score down 7pts (37 → 30)

2026-09-09

Rank Moved

Rank dropped 10 spots (#1149 → #1159)

2026-09-08

Rank Moved

Rank dropped 11 spots (#1138 → #1149)

2026-09-07

Rank Moved

Rank dropped 19 spots (#1119 → #1138)

2026-09-06

Rank Moved

Rank dropped 13 spots (#1106 → #1119)

2026-09-05

Rank Moved

Rank dropped 39 spots (#1067 → #1106)

2026-09-04

Rank Moved

Rank dropped 23 spots (#1044 → #1067)

2026-09-03

Rank Moved

Rank dropped 54 spots (#990 → #1044)

2026-09-02

Rank Moved

Rank dropped 46 spots (#944 → #990)

2026-09-01

Rank Moved

Rank dropped 38 spots (#906 → #944)

2026-08-31

Rank Moved

Rank dropped 28 spots (#878 → #906)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.6/10

2026-08-30

Rank Moved

Rank rose 399 spots (#1277 → #878)

2026-08-30

HVTrust Changed

HVTrust up 22.9pts (16.3 → 39.2)

2026-08-29

Rank Moved

Rank dropped 10 spots (#1267 → #1277)

2026-08-26

Rank Moved

Rank dropped 30 spots (#1222 → #1252)

2026-08-25

Rank Moved

Rank rose 29 spots (#1251 → #1222)

2026-08-17

Rank Moved

Rank dropped 59 spots (#1190 → #1249)

2026-08-17

Activity Score Changed

Activity score down 12pts (46 → 34)

2026-08-16

Rank Moved

Rank dropped 30 spots (#1160 → #1190)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank rose 14 spots (#1171 → #1157)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1100 → #1170)

2026-08-08

Rank Moved

Rank dropped 583 spots (#503 → #1086)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Voice & Conversational

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

open-claude-tag

How open-claude-tag could raise its score

Chain of custody

Source Unsigned

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How open-claude-tag compares in Voice & Conversational

Where the 33.5 comes from

HVTrust dimensions vs the Voice & Conversational average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about open-claude-tag

AI agent surface

Maintain open-claude-tag?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Voice & Conversational