Is Bitrise safe to use?

Bitrise has an HVTrust score of 48.0/100 (Grade D), ranked #957 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Bitrise?

Bitrise scores 48.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 41 GitHub stars and is categorized under MCP Servers.

Bitrise

bitrise-io/bitrise-mcp

MCP Server for the Bitrise API, enabling app management, build operations, artifact management and more.

MCP Servers Go Grade D Listed MIT

48.0/100

Rank #957 of 1328

Compare Bitrise

How does it stack up against its MCP Servers 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-08-14 · 25d ago

Recent change

Rank +9

Is Bitrise safe? Bitrise scores 48.0/100 (Grade D), ranked #957 of 1328 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.3/10; 31% of recent commits are signed; last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#551 Drawio MCP — 48.1 (D) → #552 Proxmox VE MCP Server — 48.1 (D) → #554 Browserbase MCP Server — 48.0 (D) → #555 Pty MCP — 47.9 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-08

Rank Moved

Rank dropped 14 spots (#943 → #957)

2026-09-07

Rank Moved

Rank dropped 43 spots (#900 → #943)

2026-09-06

Rank Moved

Rank dropped 12 spots (#888 → #900)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/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 Bitrise View MCP Servers Report missing data

43.0

Activity sub-score · out of 100

#553

In MCP Servers

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

2026-08-11 2026-09-08

Activity & Reach

Stars

Forks

Last Push

2026-08-14

25 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼14

was #943

Analysis

HVTrust Dimensions vs MCP Servers

48.0 / 100 · 100.0% confidence

Bitrise MCP Servers average (778 agents)

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

6.9 / 25

3.0 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.0

Maintenance60% last-push freshness · 40% commit activity

12.2 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

3.9 / 20

3.0 below avg 6.9

Activity Inputs

43.0 / 100

StarsRepository reach

9.7 / 30

FreshnessLast push recency

21.5 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

31%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 0

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is Bitrise safe?

Public trust evidence for Bitrise 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 Bitrise publish package provenance?

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

Does Bitrise have an OpenSSF Scorecard?

Bitrise has an OpenSSF Scorecard score of 4.3/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 Bitrise actively maintained?

Maintained. Last push was 25 days ago.

What license does Bitrise use?

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

Are Bitrise's commits signed?

31% of the last 100 commits to Bitrise 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

high confidence

Implemented

Bitrise appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

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

Maintain Bitrise?

For maintainers

HVTrust scores Bitrise 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-09-08

Rank Moved

Rank dropped 14 spots (#943 → #957)

2026-09-07

Rank Moved

Rank dropped 43 spots (#900 → #943)

2026-09-06

Rank Moved

Rank dropped 12 spots (#888 → #900)

2026-09-05

Rank Moved

Rank dropped 58 spots (#830 → #888)

2026-09-04

Rank Moved

Rank dropped 38 spots (#792 → #830)

2026-09-03

Rank Moved

Rank dropped 44 spots (#748 → #792)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.3/10

2026-09-02

Rank Moved

Rank rose 489 spots (#1237 → #748)

2026-09-02

HVTrust Changed

HVTrust up 27.7pts (20.7 → 48.4)

2026-09-01

Rank Moved

Rank dropped 22 spots (#1215 → #1237)

2026-08-31

Rank Moved

Rank dropped 22 spots (#1193 → #1215)

2026-08-30

Rank Moved

Rank dropped 27 spots (#1166 → #1193)

2026-08-29

Rank Moved

Rank dropped 27 spots (#1139 → #1166)

2026-08-28

Rank Moved

Rank dropped 21 spots (#1118 → #1139)

2026-08-27

Rank Moved

Rank dropped 18 spots (#1100 → #1118)

2026-08-26

Rank Moved

Rank dropped 73 spots (#1027 → #1100)

2026-08-24

Rank Moved

Rank dropped 10 spots (#1015 → #1025)

2026-08-22

Rank Moved

Rank rose 32 spots (#1049 → #1017)

2026-08-17

Rank Moved

Rank rose 14 spots (#1049 → #1035)

2026-08-16

Rank Moved

Rank dropped 32 spots (#1017 → #1049)

2026-08-14

Rank Moved

Rank rose 97 spots (#1111 → #1014)

2026-08-14

Activity Score Changed

Activity score up 12pts (35 → 46)

2026-08-10

Rank Moved

Rank dropped 64 spots (#1047 → #1111)

2026-08-08

Newly Listed

First tracked at rank #1045

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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.3 · Raw JSON