Is PearAI safe to use?

PearAI has an HVTrust score of 33.4/100 (Grade D), ranked #721 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for PearAI?

PearAI scores 33.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 765 GitHub stars and is categorized under Coding Agents.

PearAI

trypear/pearai-master

Master Repo For PearAI

Coding Agents Shell Grade D Needs review Unlicensed

33.4/100

Rank #721 of 1283

Compare PearAI

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction

Listing state

Needs review

Evidence coverage

Grade B · 3/5 signals

Last push

2026-06-19 · 53d ago

Recent change

Rank +1

Is PearAI safe? PearAI scores 33.4/100 (Grade D), ranked #721 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; 14% of recent commits are signed; last pushed 2026-06-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#52 Tura — 36.0 (D) → #53 Continue — 34.7 (D) → #55 zerostack — 26.2 (D) → #56 dao-code — 25.1 (D) →

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 39 spots (#683 → #722)

2026-08-08

Rank Moved

Rank dropped 264 spots (#418 → #682)

2026-07-29

Rank Moved

Rank dropped 12 spots (#395 → #407)

Maintainer Checklist

Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.

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.

Review Flags

[4.1.1] no declared license (GitHub license field is null)

Compare with another agent Get email alerts for PearAI View Coding Agents Report missing data

44.4

Activity sub-score · out of 100

#54

In Coding Agents

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 →

Activity & Reach

Stars

765

Forks

107

Last Push

2026-06-19

53 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

Open Issues

Rank Change

▲1

was #722

Analysis

HVTrust Dimensions vs Coding Agents

33.4 / 100 · 100.0% confidence

PearAI Coding Agents average (67 agents)

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

4.6 / 25

3.1 below avg 7.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

2.6 / 17

8.5 below avg 11.1

Maintenance60% last-push freshness · 40% commit activity

8.5 / 20

6.8 below avg 15.3

AdoptionLog-scaled stars · package downloads

6.9 / 20

5.3 below avg 12.2

Activity Inputs

44.4 / 100

StarsRepository reach

17.3 / 30

FreshnessLast push recency

17.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

14%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 0

Maintained 5

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is PearAI safe?

Public trust evidence for PearAI 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 PearAI publish package provenance?

No published build provenance is currently detected for PearAI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does PearAI have an OpenSSF Scorecard?

PearAI 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 PearAI actively maintained?

Slowing down. Last push was 53 days ago — keep an eye on whether activity resumes.

What license does PearAI use?

PearAI ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are PearAI's commits signed?

14% of the last 100 commits to PearAI 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

None detected

No MCP server signal detected.

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

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 PearAI'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-06-16

Activity Resumed

Activity resumed

2026-06-15

Activity Went Stale

No commits for 170 days

2026-06-13

Activity Resumed

Activity resumed

Maintain PearAI?

For maintainers

HVTrust scores PearAI 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-08-10

Rank Moved

Rank dropped 39 spots (#683 → #722)

2026-08-08

Rank Moved

Rank dropped 264 spots (#418 → #682)

2026-07-29

Rank Moved

Rank dropped 12 spots (#395 → #407)

2026-07-15

Rank Moved

Rank dropped 26 spots (#358 → #384)

2026-07-14

Rank Moved

Rank dropped 20 spots (#338 → #358)

2026-07-13

Rank Moved

Rank dropped 35 spots (#303 → #338)

2026-06-24

Rank Moved

Rank dropped 34 spots (#260 → #294)

2026-06-23

Rank Moved

Rank dropped 22 spots (#238 → #260)

2026-06-22

Rank Moved

Rank dropped 11 spots (#227 → #238)

2026-06-21

Rank Moved

Rank dropped 13 spots (#214 → #227)

2026-06-19

Activity Score Changed

Activity score up 10pts (51 → 61)

2026-06-16

Activity Resumed

Activity resumed

2026-06-16

Rank Moved

Rank rose 14 spots (#213 → #199)

2026-06-16

HVTrust Changed

HVTrust up 11.2pts (24.9 → 36.1)

2026-06-16

Activity Score Changed

Activity score up 23pts (29 → 52)

2026-06-15

Activity Went Stale

No commits for 170 days

2026-06-15

Rank Moved

Rank dropped 14 spots (#199 → #213)

2026-06-15

HVTrust Changed

HVTrust down 11.2pts (36.1 → 24.9)

2026-06-15

Activity Score Changed

Activity score down 23pts (52 → 29)

2026-06-13

Activity Resumed

Activity resumed

2026-06-13

Rank Moved

Rank rose 10 spots (#210 → #200)

2026-06-13

HVTrust Changed

HVTrust up 11.1pts (25.1 → 36.2)

2026-06-13

Activity Score Changed

Activity score up 23pts (29 → 52)

2026-06-03

Warning Issued

Warning: eligibility issues detected

2026-06-02

Rank Moved

Rank dropped 17 spots (#173 → #190)

2026-06-01

Rank Moved

Rank dropped 15 spots (#158 → #173)

2026-05-29

Rank Moved

Rank dropped 12 spots (#150 → #162)

2026-05-27

Scorecard Added

OSSF Scorecard: 2.8/10

2026-05-27

Grade Changed

Trust grade D → C

2026-05-27

HVTrust Changed

HVTrust up 14.6pts (10.5 → 25.1)

2026-05-25

Newly Listed

First tracked at rank #159

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/pearai.svg)](https://hvtracker.net/agents/pearai)
            
HTML:
            <a href="https://hvtracker.net/agents/pearai"><img src="https://hvtracker.net/badge/pearai.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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