Is Roslyn CodeLens safe to use?

Roslyn CodeLens has an HVTrust score of 83.3/100 (Grade A), ranked #110 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Roslyn CodeLens?

Roslyn CodeLens scores 83.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 54 GitHub stars and is categorized under MCP Servers.

Roslyn CodeLens

MarcelRoozekrans/roslyn-codelens-mcp

Roslyn-based MCP server giving AI agents deep semantic understanding of .NET/C# codebases — 67 tools for navigation, call graphs, diagnostics & code fixes, safe refactoring, code-quality auditing, test intelligence, DI graphs, and IL/external-assembly inspection.

MCP Servers C# Listed MIT

Is Roslyn CodeLens safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.9 / 10

Provenance Attested

Signed commits 100%

Last push yesterday

Compare Roslyn CodeLens

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Roslyn CodeLens scores 83.3/100 (Grade A), ranked #110 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.9/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Roslyn CodeLens compares in MCP Servers

#45 Markdown Vault MCP 83.4 +0.1
#46 Zotero MCP 83.4 +0.1
#47 Roslyn CodeLens 83.3 this agent
#48 CrowdStrike Falcon MCP Server 83.0 −0.3
#49 Awkoy Notion MCP Server 83.0 −0.3

Bars show each HVTrust score; the tick marks Roslyn CodeLens’s 83.3.

Where the 83.3 comes from

HVTrust dimensions vs the MCP Servers average

83.3 / 100 · 100.0% confidence

Roslyn CodeLens MCP Servers average (775 agents)

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

19.9 / 25

9.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.5 / 17

1.3 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.1 / 20

7.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.1 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

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 → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.9/10. Tighten the weakest checks to improve public safety evidence.

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

63.5

Activity sub-score · out of 100

#47

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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 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-09-25

yesterday

Commits (4 wk)

Downloads (7d)

144

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #109

Analysis

Activity Inputs

63.5 / 100

StarsRepository reach

10.4 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.5 / 25

CommunityFork signal

5.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.9 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 5

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 5

Common questions about Roslyn CodeLens

Public supply-chain signals for Roslyn CodeLens are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Roslyn CodeLens carries less obvious unverified-evidence risk than projects with thin signals.

Does Roslyn CodeLens publish package provenance?

Yes. Roslyn CodeLens's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Roslyn CodeLens have an OpenSSF Scorecard?

Roslyn CodeLens has an OpenSSF Scorecard score of 5.9/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 Roslyn CodeLens actively maintained?

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

What license does Roslyn CodeLens use?

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

Are Roslyn CodeLens's commits signed?

100% of the last 100 commits to Roslyn CodeLens 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

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

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Roslyn CodeLens'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 → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Roslyn CodeLens?

For maintainers

HVTrust scores Roslyn CodeLens 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 → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 593 spots (#699 → #106)

2026-09-23

HVTrust Changed

HVTrust up 52.3pts (30.9 → 83.2)

2026-09-22

Newly Listed

First tracked at rank #699

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank dropped 10 spots (#99 → #109)

2026-09-18

Rank Moved

Rank rose 18 spots (#117 → #99)

2026-09-07

Rank Moved

Rank dropped 10 spots (#107 → #117)

2026-09-05

Rank Moved

Rank dropped 26 spots (#81 → #107)

2026-09-03

Grade Changed

Trust grade C → A

2026-09-03

Rank Moved

Rank rose 505 spots (#579 → #74)

2026-09-03

HVTrust Changed

HVTrust up 27.5pts (54.6 → 82.1)

2026-09-02

Rank Moved

Rank dropped 30 spots (#549 → #579)

2026-09-01

Rank Moved

Rank dropped 14 spots (#535 → #549)

2026-08-31

Scorecard Added

OSSF Scorecard: 5.6/10

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 156 spots (#691 → #535)

2026-08-31

HVTrust Changed

HVTrust up 7.9pts (47.0 → 54.9)

2026-08-30

Rank Moved

Rank dropped 25 spots (#666 → #691)

2026-08-29

Rank Moved

Rank dropped 43 spots (#623 → #666)

2026-08-28

Rank Moved

Rank dropped 21 spots (#602 → #623)

2026-08-27

Rank Moved

Rank dropped 16 spots (#586 → #602)

2026-08-26

Rank Moved

Rank dropped 85 spots (#501 → #586)

2026-08-24

Rank Moved

Rank dropped 12 spots (#488 → #500)

2026-08-22

Rank Moved

Rank rose 13 spots (#503 → #490)

2026-08-19

Rank Moved

Rank dropped 13 spots (#488 → #501)

2026-08-17

Rank Moved

Rank rose 12 spots (#500 → #488)

2026-08-13

Rank Moved

Rank dropped 14 spots (#479 → #493)

2026-08-12

Rank Moved

Rank rose 15 spots (#494 → #479)

2026-08-10

Rank Moved

Rank dropped 19 spots (#475 → #494)

2026-08-08

Newly Listed

First tracked at rank #472

GitHub → npm: roslyn-codelens-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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