Is Junie safe to use?

Junie has an HVTrust score of 60.0/100 (Grade C), ranked #313 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Junie?

Junie scores 60.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 362 GitHub stars and is categorized under Coding Agents.

Junie

JetBrains/junie

An AI coding agent by JetBrains that ships code from your terminal, IDE, or CI/CD pipeline - powered by any LLM you choo

Coding Agents Shell Grade C Listed NOASSERTION Proprietary

60.0/100

Rank #313 of 1204

Compare Junie

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Rank +2

Is Junie safe? Junie scores 60.0/100 (Grade C), ranked #313 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.2/10; 1% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#24 Archon — 61.9 (C) → #25 Potpie — 61.7 (C) → #27 Stagewise — 59.7 (C) → #28 Nanocoder — 59.5 (C) →

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 78 spots (#236 → #314)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI

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.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.

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

72.2

Activity sub-score · out of 100

#26

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

362

Forks

Last Push

2026-08-09

today

Commits (4 wk)

689

Downloads (7d)

826

npm

HN mentions (30d)

172

Open Issues

Rank Change

▲1

was #314

Analysis

HVTrust Dimensions vs Coding Agents

60.0 / 100 · 100.0% confidence

Junie Coding Agents average (65 agents)

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

4.0 / 25

3.9 below avg 7.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

11.2 / 17

in line with avg 11.2

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.9 above avg 15.1

AdoptionLog-scaled stars · package downloads

10.0 / 20

2.3 below avg 12.3

Activity Inputs

72.2 / 100

StarsRepository reach

15.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

6.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.2 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 10

Is Junie safe?

Proprietary software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Junie may have internal security practices not visible through public signals.

Junie 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 Junie publish package provenance?

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

Does Junie have an OpenSSF Scorecard?

Junie has an OpenSSF Scorecard score of 3.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 Junie actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Junie use?

Junie ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Junie's commits signed?

1% of the last 100 commits to Junie 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

high confidence

Match

Published package metadata matches the tracked repo

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 Junie'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

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI

Maintain Junie?

For maintainers

HVTrust scores Junie 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-08

Rank Moved

Rank dropped 78 spots (#236 → #314)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, OpenAI

2026-07-15

Rank Moved

Rank dropped 10 spots (#213 → #223)

2026-07-14

Rank Moved

Rank dropped 12 spots (#201 → #213)

2026-07-13

Rank Moved

Rank dropped 27 spots (#174 → #201)

2026-06-24

Rank Moved

Rank dropped 22 spots (#181 → #203)

2026-06-23

Rank Moved

Rank dropped 10 spots (#171 → #181)

2026-06-18

Rank Moved

Rank dropped 13 spots (#138 → #151)

2026-06-08

Newly Listed

First tracked at rank #137

2026-06-07

Removed From Active Tracking

Removed from active tracking

2026-06-06

Newly Listed

First tracked at rank #137

GitHub → npm: @jetbrains/junie

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON