AstrBot

AI Agent Assistant & development framework that integrates lots of IM platforms, LLMs, plugins and AI feature, and can b

Voice & Conversational Python Grade C Listed AGPL-3.0
63.9/100
Rank #170 of 468
Compare AstrBot

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-05 · 1d ago
Recent change
No recent signal change

Is AstrBot safe? AstrBot scores 63.9/100 (Grade C), ranked #170 of 468 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.3/10; 92% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Voice & Conversational

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-07-17
Grade Changed
Trust grade B → C
2026-07-16
Grade Changed
Trust grade C → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/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.
93.5
Activity sub-score · out of 100
#3

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-08-06 05:00 UTC · Repo last pushed yesterday

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
38.7k
Forks
2.8k
Last Push
2026-08-05
yesterday
Commits (4 wk)
131
Downloads (7d)
HN mentions (30d)
Open Issues
1018
Rank Change
▼1
was #169

Analysis

HVTrust Dimensions vs Voice & Conversational

63.9 / 100 · 100.0% confidence

AstrBot Voice & Conversational average (8 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.2 / 25
in line with avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
0.6 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.8 above avg 17.1
AdoptionLog-scaled stars · package downloads
11.0 / 20
1.3 below avg 12.3

Activity Inputs

93.5 / 100
StarsRepository reach
27.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
OpenSSF Scorecard · scanned Aug 5, 2026
Signed Commits
92%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 2
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 10
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is AstrBot safe?

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

Compare AstrBot head-to-head

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
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Marketplace
Marketplace 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 AstrBot'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-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, Postgres

Maintain AstrBot?

For maintainers

HVTrust scores AstrBot 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.

Reputation Timeline

Signal history
Grade 4Rank 3Listed 1HVTrust 1Scorecard 1Surface 1Surface 1
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-07-17
Grade Changed
Trust grade B → C
2026-07-16
Grade Changed
Trust grade C → B
2026-07-13
Rank Moved
Rank dropped 14 spots (#126 → #140)
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, Postgres
2026-06-24
Grade Changed
Trust grade C → B
2026-06-23
Scorecard Added
OSSF Scorecard: 5.3/10
2026-06-23
Grade Changed
Trust grade D → C
2026-06-23
Rank Moved
Rank rose 131 spots (#255 → #124)
2026-06-23
HVTrust Changed
HVTrust up 38.0pts (26.9 → 64.9)
2026-06-22
Rank Moved
Rank dropped 10 spots (#245 → #255)
2026-06-21
Newly Listed
First tracked at rank #245

Embed Badge Badge guide for maintainers →

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

Other agents in Voice & Conversational

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.2 · Raw JSON