updated 2026-10-10 20:07 UTC

Beacon Skill

Repository Website

Beacon - agent-to-agent pings with optional RTC value attached (BoTTube/Moltbook/RustChain + UDP bus)

Agent Skills Python Listed MIT

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

OSSF Scorecard 5.5 / 10
Provenance None
Signed commits 70%
Last push 3d ago
Advisories None known
Compare Beacon Skill

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Beacon Skill scores 63.5/100 (Grade C), ranked #72 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 70% of recent commits are signed; no published advisory affects its latest release (beacon-skill, beacon-skill); last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Beacon Skill and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/Scottcjn/beacon-skill, MIT, last pushed 2026-10-07. 70% 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.5/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    • npm beacon-skill Source link points back to this repo No build attestation
    • PyPI beacon-skill Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest releases checked: beacon-skill 2.16.0, beacon-skill 2.16.1. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 5.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Beacon 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 Beacon Skill compares in Agent Skills

  1. #70 Citadel 63.6 +0.1
  2. #71 Archify 63.6 +0.1
  3. #72 Beacon Skill 63.5 this agent
  4. #73 Text To Cad 63.2 −0.3
  5. #74 Cloudflare Skills 63.1 −0.4

Bars show each HVTrust score; the tick marks Beacon Skill’s 63.5.

Where the 63.5 comes from

HVTrust dimensions vs the Agent Skills average

63.5 / 100 · 100.0% confidence

Beacon Skill Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 25
2.6 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
13.2 / 17
1.2 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
16.2 / 20
2.1 above avg 14.1
AdoptionLog-scaled stars · package downloads
8.9 / 20
in line with 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-26
Rank Moved
Rank rose 10 spots (#81 → #71)
2026-09-25
Rank Moved
Rank dropped 14 spots (#67 → #81)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/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 Beacon Skill View Agent Skills Report missing data
62.4
Activity sub-score · out of 100
#72
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-10 20:07 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
238
Forks
111
Last Push
2026-10-07
3 days ago
Commits (4 wk)
12
Downloads (7d)
233
npm+pypi
HN mentions (30d)
—
Open Issues
15
Rank Change
▼5
was #67

Analysis

Activity Inputs

62.4 / 100
StarsRepository reach
14.3 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
9.5 / 20

Common questions about Beacon Skill

Beacon Skill 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 Beacon Skill publish package provenance?
No published build provenance is currently detected for Beacon 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 Beacon Skill have an OpenSSF Scorecard?
Beacon Skill has an OpenSSF Scorecard score of 5.5/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 Beacon Skill actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Beacon Skill use?
Beacon Skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Beacon Skill's commits signed?
70% of the last 100 commits to Beacon 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
medium 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
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
high confidence
Match
Published package metadata matches the tracked repo
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 Beacon 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
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain Beacon Skill?

For maintainers

HVTrust scores Beacon 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
Rank 10Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1
2026-09-26
Rank Moved
Rank rose 10 spots (#81 → #71)
2026-09-25
Rank Moved
Rank dropped 14 spots (#67 → #81)
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 rose 206 spots (#274 → #68)
2026-09-23
HVTrust Changed
HVTrust up 33.5pts (29.7 → 63.2)
2026-09-22
Newly Listed
First tracked at rank #274
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 14 spots (#100 → #86)
2026-09-14
Rank Moved
Rank dropped 16 spots (#89 → #105)
2026-09-13
Rank Moved
Rank rose 15 spots (#104 → #89)
2026-09-11
Rank Moved
Rank dropped 25 spots (#77 → #102)
2026-09-05
Rank Moved
Rank dropped 13 spots (#50 → #63)
2026-08-28
Scorecard Added
OSSF Scorecard: 5.5/10
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 72 spots (#110 → #38)
2026-08-28
HVTrust Changed
HVTrust up 26.9pts (33.2 → 60.1)
2026-08-27
Rank Moved
Rank dropped 22 spots (#88 → #110)
2026-08-26
Newly Listed
First tracked at rank #88
GitHub → Website → PyPI: beacon-skill npm: beacon-skill

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/beacon-skill.svg)](https://hvtracker.net/agents/beacon-skill)
HTML:
<a href="https://hvtracker.net/agents/beacon-skill"><img src="https://hvtracker.net/badge/beacon-skill.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON