Is Claude to IM skill safe to use?

Claude to IM skill has an HVTrust score of 31.9/100 (Grade D), ranked #354 of 371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude to IM skill?

Claude to IM skill scores 31.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.9k GitHub stars and is categorized under Agent Skills.

Claude to IM skill

Repository by op7418

Bridge Claude Code / Codex to IM platforms — chat with AI coding agents from Telegram, Discord, or Feishu/Lark.

Agent Skills TypeScript Listed MIT

Is Claude to IM skill safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10

Provenance None

Signed commits 6%

Last push 201d ago

Compare Claude to IM skill

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Claude to IM skill scores 31.9/100 (Grade D), ranked #354 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 2.6/10; 6% of recent commits are signed; last pushed 2026-03-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude to IM skill 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, CI-Tests 0, CII-Best-Practices 0 +13.4 → 45.3 D · #291 of 371
Sign every commit6% signed today +4.6 → 36.5 D · #343 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Claude to IM skill 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.

Source Partly signed

github.com/op7418/Claude-to-IM-skill, MIT, last pushed 2026-03-23. 6% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

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

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 9
Published packages None

No registry package. Claude to IM skill 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-01 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 Claude to IM skill’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 to IM skill compares in Agent Skills

Bars show each HVTrust score; the tick marks Claude to IM skill’s 31.9.

Where the 31.9 comes from

HVTrust dimensions vs the Agent Skills average

31.9 / 100 · 100.0% confidence

Claude to IM skill Agent Skills average (371 agents)

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

3.6 / 25

4.2 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

10.7 / 17

1.3 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.1 below avg 14.1

AdoptionLog-scaled stars · package downloads

8.3 / 20

0.7 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

HVTrust Changed

HVTrust up 11.1pts (20.8 → 31.9)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

HVTrust Changed

HVTrust up 4.5pts (16.3 → 20.8)

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 201 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Claude to IM skill View Agent Skills Report missing data

32.4

Activity sub-score · out of 100

#354

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 →

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars

2.9k

Forks

316

Last Push

2026-03-23

201 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #351

Analysis

Activity Inputs

32.4 / 100

StarsRepository reach

20.8 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.6 / 20

Common questions about Claude to IM skill

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

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

Claude to IM skill 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 Claude to IM skill actively maintained?

Stale. The repository has not been pushed to in 201 days. Consider whether the project is still being maintained.

What license does Claude to IM skill use?

Claude to IM skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Claude to IM skill's commits signed?

6% of the last 100 commits to Claude to IM skill 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 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 Claude to IM skill'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, OpenAI

Maintain Claude to IM skill?

For maintainers

HVTrust scores Claude to IM skill 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-09-25

HVTrust Changed

HVTrust up 11.1pts (20.8 → 31.9)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

HVTrust Changed

HVTrust up 4.5pts (16.3 → 20.8)

2026-09-22

Newly Listed

First tracked at rank #346

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-08

Rank Moved

Rank dropped 22 spots (#317 → #339)

2026-09-01

Scorecard Added

OSSF Scorecard: 2.6/10

2026-09-01

Rank Moved

Rank rose 43 spots (#329 → #286)

2026-09-01

HVTrust Changed

HVTrust up 11.4pts (10.2 → 21.6)

2026-08-26

Newly Listed

First tracked at rank #329

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/claude-to-im-skill.svg)](https://hvtracker.net/agents/claude-to-im-skill)
            
HTML:
            <a href="https://hvtracker.net/agents/claude-to-im-skill"><img src="https://hvtracker.net/badge/claude-to-im-skill.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

Claude to IM skill

How Claude to IM skill could raise its score

Chain of custody

Source Partly signed

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 Claude to IM skill compares in Agent Skills

Where the 31.9 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Claude to IM skill

AI agent surface

Maintain Claude to IM skill?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills