Is Claude Elixir Phoenix safe to use?

Claude Elixir Phoenix has an HVTrust score of 57.9/100 (Grade C), ranked #136 of 384 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude Elixir Phoenix?

Claude Elixir Phoenix scores 57.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 574 GitHub stars and is categorized under Agent Skills.

Claude Elixir Phoenix

Repository Website

Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute with automatic verification, review with 4-agent parallel audits, and capture learnings as reusable knowledge.

Agent Skills Python Listed MIT

Is Claude Elixir Phoenix safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.6 / 10

Provenance None

Signed commits 87%

Last push 4d ago

Compare Claude Elixir Phoenix

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Claude Elixir Phoenix scores 57.9/100 (Grade C), ranked #136 of 384 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.6/10; 87% of recent commits are signed; last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Elixir Phoenix 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 5.6 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +7.1 → 65.0 B · #63 of 384
Sign every commit87% signed today +0.7 → 58.6 C · #126 of 384

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Claude Elixir Phoenix 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 Signed

github.com/oliver-kriska/claude-elixir-phoenix, MIT, last pushed 2026-11-06. 87% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies7
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 7

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 7
Published packages None

No registry package. Claude Elixir Phoenix 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-08-27 OSSF Scorecard: 5.9/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 Elixir Phoenix’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 Elixir Phoenix compares in Agent Skills

#134 oh-my-hermes 58.2 +0.3
#135 Sepia 58.0 +0.1
#136 Claude Elixir Phoenix 57.9 this agent
#137 Jakub Krehel Skills 57.9 ±0
#138 Claude Code Workflows 57.7 −0.2

Bars show each HVTrust score; the tick marks Claude Elixir Phoenix’s 57.9.

Where the 57.9 comes from

HVTrust dimensions vs the Agent Skills average

57.9 / 100 · 100.0% confidence

Claude Elixir Phoenix Agent Skills average (384 agents)

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

11.3 / 25

3.1 above avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.1 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.2 / 20

2.2 above avg 14.0

AdoptionLog-scaled stars · package downloads

6.6 / 20

2.5 below avg 9.1

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.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.

Compare with another agent View Agent Skills Report missing data

62.8

Activity sub-score · out of 100

#136

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 →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

574

Forks

Last Push

2026-11-06

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #136

Analysis

Activity Inputs

62.8 / 100

StarsRepository reach

16.6 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

13.9 / 25

CommunityFork signal

7.7 / 20

Common questions about Claude Elixir Phoenix

Claude Elixir Phoenix 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 Claude Elixir Phoenix publish package provenance?

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

Claude Elixir Phoenix has an OpenSSF Scorecard score of 5.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 Elixir Phoenix actively maintained?

Actively maintained. The repository was pushed to within the last 4 day(s).

What license does Claude Elixir Phoenix use?

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

Are Claude Elixir Phoenix's commits signed?

87% of the last 100 commits to Claude Elixir Phoenix 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

low confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high 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

How this surface has changed

Detected changes to Claude Elixir Phoenix'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Claude Elixir Phoenix?

For maintainers

HVTrust scores Claude Elixir Phoenix 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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 50 spots (#78 → #128)

2026-09-23

HVTrust Changed

HVTrust up 10.6pts (45.7 → 56.3)

2026-09-22

Newly Listed

First tracked at rank #78

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 25 spots (#107 → #132)

2026-09-05

Rank Moved

Rank dropped 12 spots (#58 → #70)

2026-08-27

Scorecard Added

OSSF Scorecard: 5.9/10

2026-08-27

Grade Changed

Trust grade D → C

2026-08-27

Rank Moved

Rank rose 139 spots (#172 → #33)

2026-08-27

HVTrust Changed

HVTrust up 36.3pts (22.9 → 59.2)

2026-08-26

Rank Moved

Rank dropped 83 spots (#89 → #172)

2026-08-23

Rank Moved

Rank dropped 13 spots (#69 → #82)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

How Claude Elixir Phoenix could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Claude Elixir Phoenix compares in Agent Skills

Where the 57.9 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Claude Elixir Phoenix

AI agent surface

Maintain Claude Elixir Phoenix?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills