Julep

Julep — durable, composable AI agents. Flows that crash and resume, retry safely, and explain every step.

Workflow Platforms Python Grade C Listed Apache-2.0
56.7/100
Rank #367 of 1204
Compare Julep

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-06 · 3d ago
Recent change
Rank +2

Is Julep safe? Julep scores 56.7/100 (Grade C), ranked #367 of 1204 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.2/10; 9% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 96 spots (#267 → #363)
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependencies: Groq, Multi-provider (LiteLLM), OpenRouter, Postgres
2026-08-07
Scorecard Added
OSSF Scorecard: 5.4/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/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.
86.4
Activity sub-score · out of 100
#16

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-09 19:01 UTC · Repo last pushed 3 days ago

Activity & Reach

Stars
6.6k
Forks
969
Last Push
2026-08-06
3 days ago
Commits (4 wk)
155
Downloads (7d)
HN mentions (30d)
Open Issues
1
Rank Change
▼4
was #363

Analysis

HVTrust Dimensions vs Workflow Platforms

56.7 / 100 · 100.0% confidence

Julep Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.0 / 25
3.3 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.8 / 20
1.6 above avg 18.2
AdoptionLog-scaled stars · package downloads
9.2 / 20
3.7 below avg 12.8

Activity Inputs

86.4 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.9 / 20

Supply Chain Trust

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

Is Julep safe?

Julep 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 Julep publish package provenance?
No published build provenance is currently detected for Julep. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Julep have an OpenSSF Scorecard?
Julep has an OpenSSF Scorecard score of 5.2/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 Julep actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Julep use?
Julep ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Julep's commits signed?
9% of the last 100 commits to Julep 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
high confidence
7 detected
Public provider/service dependencies 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 Julep'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-08-07
Provider Added
Runtime surface grew — new detected provider dependencies: Groq, Multi-provider (LiteLLM), OpenRouter, Postgres

Maintain Julep?

For maintainers

HVTrust scores Julep 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 4Listed 1Scorecard 1Surface 1
2026-08-08
Rank Moved
Rank dropped 96 spots (#267 → #363)
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependencies: Groq, Multi-provider (LiteLLM), OpenRouter, Postgres
2026-08-07
Scorecard Added
OSSF Scorecard: 5.4/10
2026-07-28
Rank Moved
Rank dropped 13 spots (#409 → #422)
2026-07-15
Rank Moved
Rank dropped 15 spots (#395 → #410)
2026-07-14
Rank Moved
Rank dropped 32 spots (#363 → #395)
2026-07-13
Newly Listed
First tracked at rank #363

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

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