Parlant

Build reliable customer-facing AI agents with Parlant: an interaction control harness optimized for controlled, consiste

Agent Frameworks Python Grade D Listed Apache-2.0
45.6/100
Rank #346 of 468
Compare Parlant

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

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

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

Is Parlant safe? Parlant scores 45.6/100 (Grade D), ranked #346 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 3.7/10; 3% of recent commits are signed; last pushed 2026-07-12. 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-07-29
Rank Moved
Rank dropped 10 spots (#331 → #341)
2026-07-25
Activity Score Changed
Activity score down 5pts (72 → 67)
2026-07-15
Rank Moved
Rank dropped 23 spots (#289 → #312)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
65.9
Activity sub-score · out of 100
#73

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 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 04:30 UTC · Repo last pushed 25 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
18.2k
Forks
1.5k
Last Push
2026-07-12
25 days ago
Commits (4 wk)
1?
Downloads (7d)
HN mentions (30d)
Open Issues
19
Rank Change
=
was #346

Analysis

HVTrust Dimensions vs Agent Frameworks

45.6 / 100 · 100.0% confidence

Parlant Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.8 / 25
4.2 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
10.9 / 20
3.7 below avg 14.6
AdoptionLog-scaled stars · package downloads
10.2 / 20
1.7 below avg 11.9

Activity Inputs

65.9 / 100
StarsRepository reach
25.6 / 30
FreshnessLast push recency
21.5 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
14.8 / 20

Supply Chain Trust

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

Is Parlant safe?

Public trust evidence for Parlant 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 Parlant publish package provenance?
No published build provenance is currently detected for Parlant. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Parlant have an OpenSSF Scorecard?
Parlant has an OpenSSF Scorecard score of 3.7/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 Parlant actively maintained?
Maintained. Last push was 25 days ago.
What license does Parlant use?
Parlant ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Parlant's commits signed?
3% of the last 100 commits to Parlant 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
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • database
  • search
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 Parlant?

For maintainers

HVTrust scores Parlant 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 6Score 2Listed 1HVTrust 1Scorecard 1Grade 1
2026-07-29
Rank Moved
Rank dropped 10 spots (#331 → #341)
2026-07-25
Activity Score Changed
Activity score down 5pts (72 → 67)
2026-07-15
Rank Moved
Rank dropped 23 spots (#289 → #312)
2026-07-14
Rank Moved
Rank dropped 11 spots (#278 → #289)
2026-07-13
Rank Moved
Rank dropped 36 spots (#242 → #278)
2026-06-24
Rank Moved
Rank dropped 27 spots (#197 → #224)
2026-06-23
Grade Changed
Trust grade D → C
2026-06-23
Activity Score Changed
Activity score up 6pts (69 → 75)
2026-06-22
Scorecard Added
OSSF Scorecard: 3.7/10
2026-06-22
Rank Moved
Rank rose 96 spots (#284 → #188)
2026-06-22
HVTrust Changed
HVTrust up 28.8pts (20.9 → 49.7)
2026-06-21
Newly Listed
First tracked at rank #284

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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