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. Full methodology →
Signals refreshed2026-06-06 20:03 UTC·Repo last pushed today
Activity & Reach
Stars
276
Forks
19
Last Push
2026-06-06
today
Commits (4 wk)
494
Downloads (7d)
727
npm
HN mentions (30d)
106
Open Issues
41
Rank Change
NEW
Analysis
HVTrust Dimensions
56.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
4.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.4 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
9.7 / 20
Activity Inputs
70.7 / 100
StarsRepository reach
14.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.4 / 10
via deps.dev · OpenSSF
Signed Commits
5%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests-1
CII-Best-Practices0
Code-Review0
Contributors3
Dangerous-Workflow-1
Dependency-Update-Tool0
Fuzzing0
License9
Maintained10
Packaging-1
Pinned-Dependencies-1
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions-1
Vulnerabilities10
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.4/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?
5% 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Anthropic
OpenAI
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
shell
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
Maintain Junie?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
