updated 2026-10-09 08:15 UTC

AIlice

Repository

AIlice is a fully autonomous, general-purpose AI agent.

Agent Frameworks Python Needs review MIT

Is AIlice safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10
Provenance None
Signed commits 0%
Last push 417d ago
Compare AIlice

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: AIlice scores 24.1/100 (Grade D), ranked #1331 of 1371 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 3.1/10; recent commits are unsigned; last pushed 2025-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

How AIlice 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
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-08-18)

Chain of custody

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

  1. Source Unsigned

    github.com/myshell-ai/AIlice, MIT, last pushed 2025-08-18. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    No registry package. AIlice is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of AIlice.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues AIlice’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 tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How AIlice compares in Agent Frameworks

  1. #120 Yunjue-Agent 29.2 +5.1
  2. #121 JARVIS / HuggingGPT 26.5 +2.4
  3. #122 AIlice 24.1 this agent
  4. #123 mcp-agent 23.3 −0.8
  5. #124 AWorld 23.1 −1.0

Bars show each HVTrust score; the tick marks AIlice’s 24.1.

Where the 24.1 comes from

HVTrust dimensions vs the Agent Frameworks average

24.1 / 100 · 100.0% confidence

AIlice Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
5.6 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
0.9 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.6 below avg 13.6
AdoptionLog-scaled stars · package downloads
7.6 / 20
3.2 below avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
HVTrust Changed
HVTrust up 8.4pts (15.7 → 24.1)
2026-09-23
Rank Moved
Rank dropped 78 spots (#1245 → #1323)
2026-09-22
Rank Moved
Rank dropped 806 spots (#439 → #1245)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 417 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-08-18)
Compare with another agent Get email alerts for AIlice View Agent Frameworks Report missing data
29.7
Activity sub-score · out of 100
#122
In Agent Frameworks

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 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-09 08:15 UTC · Repo last pushed 417 days ago — may be stale

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
1.4k
Forks
207
Last Push
2025-08-18
417 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
4
Open Issues
7
Rank Change
=
was #1331

Analysis

Activity Inputs

29.7 / 100
StarsRepository reach
18.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.8 / 20

Common questions about AIlice

Public trust evidence for AIlice 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 AIlice publish package provenance?
No published build provenance is currently detected for AIlice. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AIlice have an OpenSSF Scorecard?
AIlice has an OpenSSF Scorecard score of 3.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 AIlice actively maintained?
Stale. The repository has not been pushed to in 417 days. Consider whether the project is still being maintained.
What license does AIlice use?
AIlice ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AIlice's commits signed?
0% of the last 100 commits to AIlice 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
Implemented
AIlice appears to expose MCP server capabilities.
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
1 tags
Broad capability areas detected.
  • browser
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 AIlice?

For maintainers

HVTrust scores AIlice 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 13HVTrust 2Warning Issued 1
2026-09-25
HVTrust Changed
HVTrust up 8.4pts (15.7 → 24.1)
2026-09-23
Rank Moved
Rank dropped 78 spots (#1245 → #1323)
2026-09-22
Rank Moved
Rank dropped 806 spots (#439 → #1245)
2026-09-21
Rank Moved
Rank rose 886 spots (#1325 → #439)
2026-08-26
Rank Moved
Rank dropped 21 spots (#1251 → #1272)
2026-08-19
Rank Moved
Rank dropped 428 spots (#822 → #1250)
2026-08-19
HVTrust Changed
HVTrust down 10.0pts (25.7 → 15.7)
2026-08-18
Warning Issued
Warning: eligibility issues detected
2026-08-16
Rank Moved
Rank dropped 16 spots (#816 → #832)
2026-08-12
Rank Moved
Rank rose 10 spots (#817 → #807)
2026-08-10
Rank Moved
Rank dropped 45 spots (#774 → #819)
2026-08-08
Rank Moved
Rank dropped 329 spots (#435 → #764)
2026-07-28
Rank Moved
Rank dropped 13 spots (#408 → #421)
2026-07-15
Rank Moved
Rank dropped 15 spots (#394 → #409)
2026-07-14
Rank Moved
Rank dropped 32 spots (#362 → #394)
2026-07-13
Rank Moved
Rank dropped 39 spots (#323 → #362)
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON