AIlice

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

Agent Frameworks Python Grade D Listed MIT
25.7/100
Rank #817 of 1283
Compare AIlice

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2025-08-18 · 358d ago
Recent change
Rank +1

Is AIlice safe? AIlice scores 25.7/100 (Grade D), ranked #817 of 1283 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 →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
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 358 days ago. Fresh activity helps separate stable projects from stale ones.
29.7
Activity sub-score · out of 100
#89

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-08-11 21:02 UTC · Repo last pushed 358 days ago — may be stale

Activity & Reach

Stars
1.4k
Forks
205
Last Push
2025-08-18
358 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
8
Open Issues
6
Rank Change
▲2
was #819

Analysis

HVTrust Dimensions vs Agent Frameworks

25.7 / 100 · 75.0% confidence

AIlice Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
4.2 below avg 8.1
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
in line with avg 11.6
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.4 below avg 14.4
AdoptionLog-scaled stars · package downloads
7.6 / 20
3.8 below avg 11.4

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

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.1 / 10
OpenSSF Scorecard · scanned Aug 10, 2026
Signed Commits
0%
of last 100 commits verified
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

Is AIlice safe?

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 358 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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.

Reputation Timeline

Signal history
Rank 12HVTrust 2Listed 1Grade 1Scorecard 1
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)
2026-06-24
Rank Moved
Rank dropped 31 spots (#282 → #313)
2026-06-23
Rank Moved
Rank dropped 18 spots (#264 → #282)
2026-06-21
Rank Moved
Rank dropped 16 spots (#244 → #260)
2026-06-20
Rank Moved
Rank dropped 17 spots (#227 → #244)
2026-06-02
Rank Moved
Rank dropped 17 spots (#175 → #192)
2026-06-01
Rank Moved
Rank dropped 12 spots (#163 → #175)
2026-05-29
HVTrust Changed
HVTrust up 7.5pts (17.7 → 25.2)
2026-05-27
Scorecard Added
OSSF Scorecard: 3.1/10
2026-05-27
Grade Changed
Trust grade D → C
2026-05-27
HVTrust Changed
HVTrust up 9.8pts (8.6 → 18.4)
2026-05-25
Newly Listed
First tracked at rank #161

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 25.7 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) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON