updated 2026-10-16 16:07 UTC

Archify

Repository Website

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

Agent Skills JavaScript Listed MIT

Is Archify safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.1 / 10
Provenance None
Signed commits 52%
Last push today
Compare Archify

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Archify scores 64.4/100 (Grade C), ranked #65 of 385 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 5.1/10; 52% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Archify 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

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

  1. Source Partly signed

    github.com/tt-a1i/archify, MIT, last pushed 2026-10-16. 52% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection8
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 3
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 5

  3. Published packages None

    No registry package. Archify 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-12 OSSF Scorecard: 5.2/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 Archify’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 Archify compares in Agent Skills

  1. #63 Addyosmani Agent Skills 64.6 +0.2
  2. #64 Visual Explainer 64.6 +0.2
  3. #65 Archify 64.4 this agent
  4. #66 Voyager 64.4 ±0
  5. #67 Linkedin Skills 64.2 −0.2

Bars show each HVTrust score; the tick marks Archify’s 64.4.

Where the 64.4 comes from

HVTrust dimensions vs the Agent Skills average

64.4 / 100 · 100.0% confidence

Archify Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.0 / 25
1.2 above 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
12.8 / 17
0.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
11.8 / 20
2.8 above 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-23
Grade Changed
Trust grade C → B
2026-09-23
Rank Moved
Rank dropped 44 spots (#8 → #52)
2026-09-23
HVTrust Changed
HVTrust up 12.4pts (53.5 → 65.9)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/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.
Compare with another agent Get email alerts for Archify View Agent Skills Report missing data
97.1
Activity sub-score · out of 100
#65
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 C 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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
84.4k
Forks
5.7k
Last Push
2026-10-16
today
Commits (4 wk)
1098
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
115
Rank Change
▼5
was #60

Analysis

Activity Inputs

97.1 / 100
StarsRepository reach
29.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.5 / 20

Common questions about Archify

Archify has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
Archify has an OpenSSF Scorecard score of 5.1/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 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?
52% 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
Grade 4Listed 2HVTrust 2Rank 2Scorecard 1Delisted 1
2026-09-23
Grade Changed
Trust grade C → B
2026-09-23
Rank Moved
Rank dropped 44 spots (#8 → #52)
2026-09-23
HVTrust Changed
HVTrust up 12.4pts (53.5 → 65.9)
2026-09-22
Newly Listed
First tracked at rank #8
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Grade Changed
Trust grade C → B
2026-09-13
Grade Changed
Trust grade B → C
2026-09-12
Scorecard Added
OSSF Scorecard: 5.2/10
2026-09-12
Grade Changed
Trust grade D → B
2026-09-12
Rank Moved
Rank rose 279 spots (#334 → #55)
2026-09-12
HVTrust Changed
HVTrust up 38.1pts (27.1 → 65.2)
2026-09-11
Newly Listed
First tracked at rank #334
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.4 Grade C
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON