Julep
Website
Julep — durable, composable AI agents. Flows that crash and resume, retry safely, and explain every step.
Is Julep safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Julep
How does it stack up against its Workflow Platforms neighbours?
Pick any agent to compare →In detail: Julep scores 44.1/100 (Grade D), ranked #1120 of 1371 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 4.9/10; 13% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →
How Julep 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.
- Raise the OSSF Scorecard from 4.9 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +8.5 → 52.6 C · #22 of 26
- Sign every commit13% signed today +4.3 → 48.4 D · #23 of 26
Chain of custody
Scanners check what the code says. This traces who ships Julep 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.
-
Source Partly signed
github.com/julep-ai/julep, Apache-2.0, last pushed 2026-08-06. 13% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.9/10 (scanned Sep 24, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 8Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 10Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Julep is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-07 OSSF Scorecard: 5.4/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Julep’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.
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 Julep compares in Workflow Platforms
- #22 Coze Studio 51.1 +7.0
- #23 LiteFlow 47.8 +3.7
- #24 Julep 44.1 this agent
- #25 Activepieces 41.2 −2.9
- #26 PromptFlow 40.2 −3.9
Bars show each HVTrust score; the tick marks Julep’s 44.1.
Where the 44.1 comes from
HVTrust dimensions vs the Workflow Platforms average
44.1 / 100 · 100.0% confidenceJulep Workflow Platforms average (26 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
52.6 / 100Common questions about Julep
Does Julep publish package provenance?
Does Julep have an OpenSSF Scorecard?
Is Julep actively maintained?
What license does Julep use?
Are Julep's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/julep)
<a href="https://hvtracker.net/agents/julep"><img src="https://hvtracker.net/badge/julep.svg" alt="HVTrust"></a>
Other agents in Workflow Platforms
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON