updated 2026-09-11 14:33 UTC

Archify

tt-a1i/archify

Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self-contained

Agent Skills JavaScript Grade D Listed MIT
27.1/100
Rank #332 of 354
Compare Archify

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-09-11 · 0d ago
Recent change
New

Is Archify safe? Archify scores 27.1/100 (Grade D), ranked #332 of 354 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; 69% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#330 Guizang Social Card Skill — 27.6 (D) → #331 Claude Skills — 27.5 (D) → #333 Herdr — 26.6 (D) → #334 Anthropic Cybersecurity Skills — 26.1 (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-11
Newly Listed
First tracked at rank #332
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 Archify View Agent Skills Report missing data
95.1
Activity sub-score · out of 100
#332
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-11 14:33 UTC · Repo last pushed today

Activity & Reach

Stars
58.2k
Forks
3.8k
Last Push
2026-09-11
today
Commits (4 wk)
99
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
67
Rank Change
NEW

Analysis

HVTrust Dimensions vs Agent Skills

27.1 / 100 · 50.0% confidence

Archify Agent Skills average (354 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.4 / 25
4.3 below avg 7.7
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.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.6 above avg 14.4
AdoptionLog-scaled stars · package downloads
11.4 / 20
2.6 above avg 8.8

Activity Inputs

95.1 / 100
StarsRepository reach
28.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
24.9 / 25
CommunityFork signal
16.6 / 20

Supply Chain Trust

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

Is Archify safe?

Public trust evidence for Archify 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 Archify publish package provenance?
No published build provenance is currently detected for Archify. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Archify have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Archify. 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 Archify actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Archify use?
Archify ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Archify's commits signed?
69% of the last 100 commits to Archify 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 Archify?

For maintainers

HVTrust scores Archify 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-11
Newly Listed
First tracked at rank #332
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 27.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/archify.svg)](https://hvtracker.net/agents/archify)
HTML:
<a href="https://hvtracker.net/agents/archify"><img src="https://hvtracker.net/badge/archify.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