Is Logoloom safe to use?

Logoloom has an HVTrust score of 30.5/100 (Grade D), ranked #1285 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Logoloom?

Logoloom scores 30.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 42 GitHub stars and is categorized under MCP Servers.

Logoloom

mcpware/logoloom

AI-powered logo design → SVG → full brand kit. Free, local, MCP-native.

MCP Servers JavaScript Listed MIT

Is Logoloom safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.6 / 10

Provenance None

Signed commits 0%

Last push 187d ago

Compare Logoloom

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Logoloom scores 30.5/100 (Grade D), ranked #1285 of 1325 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 3.6/10; recent commits are unsigned; last pushed 2026-03-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Logoloom compares in MCP Servers

#764 MCP Server Taiwan Weather 30.9 +0.4
#765 PapersFlow 30.6 +0.1
#766 Logoloom 30.5 this agent
#767 Operant MCP 30.5 ±0
#768 Connectrylab Architect Cert MCP 30.0 −0.5

Bars show each HVTrust score; the tick marks Logoloom’s 30.5.

Where the 30.5 comes from

HVTrust dimensions vs the MCP Servers average

30.5 / 100 · 100.0% confidence

Logoloom MCP Servers average (775 agents)

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

4.5 / 25

5.8 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

3.9 / 20

3.3 below avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.6/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.

Refresh maintenance signals The repo was last pushed 187 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Logoloom View MCP Servers Report missing data

14.6

Activity sub-score · out of 100

#766

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

Activity & Reach

Stars

Forks

Last Push

2026-03-23

187 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #1287

Analysis

Activity Inputs

14.6 / 100

StarsRepository reach

9.8 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Sep 25, 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 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Common questions about Logoloom

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

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

Does Logoloom have an OpenSSF Scorecard?

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

Stale. The repository has not been pushed to in 187 days. Consider whether the project is still being maintained.

What license does Logoloom use?

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

Are Logoloom's commits signed?

0% of the last 100 commits to Logoloom 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

Declared

Declared plugin/integration 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 Logoloom'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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Logoloom?

For maintainers

HVTrust scores Logoloom 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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank dropped 192 spots (#1093 → #1285)

2026-09-23

HVTrust Changed

HVTrust up 8.2pts (22.3 → 30.5)

2026-09-22

Newly Listed

First tracked at rank #1093

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-08

Rank Moved

Rank dropped 12 spots (#1253 → #1265)

2026-09-07

Rank Moved

Rank dropped 11 spots (#1242 → #1253)

2026-09-06

Rank Moved

Rank dropped 17 spots (#1225 → #1242)

2026-09-05

Rank Moved

Rank dropped 22 spots (#1203 → #1225)

2026-09-04

Rank Moved

Rank dropped 17 spots (#1186 → #1203)

2026-09-03

Rank Moved

Rank dropped 43 spots (#1143 → #1186)

2026-09-02

Scorecard Added

OSSF Scorecard: 3.6/10

2026-09-02

Rank Moved

Rank rose 172 spots (#1315 → #1143)

2026-09-02

HVTrust Changed

HVTrust up 19.6pts (11.8 → 31.4)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1276 → #1301)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1196 → #1275)

2026-08-08

Newly Listed

First tracked at rank #1196

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/logoloom.svg)](https://hvtracker.net/agents/logoloom)
            
HTML:
            <a href="https://hvtracker.net/agents/logoloom"><img src="https://hvtracker.net/badge/logoloom.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