updated 2026-09-08 22:03 UTC

Icm Architect

RinDig/icm-architect

Claude skill: design any process, idea, or problem into an ICM workspace (folder structure as agent architecture), or re

Agent Skills Grade D Listed MIT
21.5/100
Rank #337 of 351
Compare Icm Architect

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-25 · 14d ago
Recent change
New

Is Icm Architect safe? Icm Architect scores 21.5/100 (Grade D), ranked #337 of 351 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; 62% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#335 Autoprompt Skill — 21.9 (D) → #336 Design Judge Skills — 21.8 (D) → #338 Notfair Plugin — 21.3 (D) → #339 Claude to IM skill — 21.2 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-08
Newly Listed
First tracked at rank #337
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.
Compare with another agent Get email alerts for Icm Architect View Agent Skills Report missing data
58.9
Activity sub-score · out of 100
#337
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 →

Signals refreshed 2026-09-08 22:03 UTC · Repo last pushed 14 days ago

Activity & Reach

Stars
1.5k
Forks
207
Last Push
2026-08-25
14 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
NEW

Analysis

HVTrust Dimensions vs Agent Skills

21.5 / 100 · 50.0% confidence

Icm Architect Agent Skills average (351 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.1 / 25
4.3 below avg 7.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.0 / 20
1.4 below avg 14.4
AdoptionLog-scaled stars · package downloads
7.6 / 20
1.2 below avg 8.8

Activity Inputs

58.9 / 100
StarsRepository reach
19.0 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
10.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
62%
of last 100 commits verified

Is Icm Architect safe?

Public trust evidence for Icm Architect 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 Icm Architect publish package provenance?
No published build provenance is currently detected for Icm Architect. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Icm Architect have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Icm Architect. 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 Icm Architect actively maintained?
Maintained. Last push was 14 days ago.
What license does Icm Architect use?
Icm Architect ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Icm Architect's commits signed?
62% of the last 100 commits to Icm Architect 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
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 Icm Architect?

For maintainers

HVTrust scores Icm Architect 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
Listed 1
2026-09-08
Newly Listed
First tracked at rank #337
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 21.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/icm-architect.svg)](https://hvtracker.net/agents/icm-architect)
HTML:
<a href="https://hvtracker.net/agents/icm-architect"><img src="https://hvtracker.net/badge/icm-architect.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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