Is open-claude-tag safe to use?

open-claude-tag has an HVTrust score of 17.6/100 (Grade D), ranked #1171 of 1283 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 17.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 911 GitHub stars and is categorized under Voice & Conversational.

open-claude-tag

Anil-matcha/open-claude-tag

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

Voice & Conversational Python Grade D Listed MIT

17.6/100

Rank #1171 of 1283

Compare open-claude-tag

How does it stack up against its Voice & Conversational 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-06-25 · 47d ago

Recent change

Rank +2

Is open-claude-tag safe? open-claude-tag scores 17.6/100 (Grade D), ranked #1171 of 1283 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; 49% of recent commits are signed; last pushed 2026-06-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Voice & Conversational

#7 Call Center AI — 48.0 (D) → #8 Leon — 39.8 (D) → #9 py-xiaozhi — 24.6 (D) → #10 MaiBot — 23.5 (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-10

Rank Moved

Rank dropped 70 spots (#1100 → #1170)

2026-08-08

Rank Moved

Rank dropped 583 spots (#503 → #1086)

2026-08-06

Newly Listed

First tracked at rank #507

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.

Refresh maintenance signals The repo was last pushed 47 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for open-claude-tag View Voice & Conversational Report missing data

46.9

Activity sub-score · out of 100

#11

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 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

911

Forks

191

Last Push

2026-06-25

47 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1170

Analysis

HVTrust Dimensions vs Voice & Conversational

17.6 / 100 · 50.0% confidence

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

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

2.5 / 25

6.3 below avg 8.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.2 below avg 11.7

Maintenance60% last-push freshness · 40% commit activity

8.9 / 20

7.8 below avg 16.7

AdoptionLog-scaled stars · package downloads

7.1 / 20

4.1 below avg 11.2

Activity Inputs

46.9 / 100

StarsRepository reach

17.8 / 30

FreshnessLast push recency

18.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

49%

of last 100 commits verified

Is open-claude-tag safe?

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?

No OpenSSF Scorecard data is currently published for open-claude-tag. 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 open-claude-tag actively maintained?

Slowing down. Last push was 47 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?

49% 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

medium 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

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-08-10

Rank Moved

Rank dropped 70 spots (#1100 → #1170)

2026-08-08

Rank Moved

Rank dropped 583 spots (#503 → #1086)

2026-08-06

Newly Listed

First tracked at rank #507

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON