Is Angular Signal Forms Migration safe and trustworthy?

tashan scores Angular Signal Forms Migration on public evidence — tashan score 48.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Angular Signal Forms Migration?

In Claude Code: run `claude mcp add angular-signal-forms-migration -- npx -y angular-signal-forms-migration-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Angular Signal Forms Migration?

source: Alvi97/angular-signal-forms-migration-mcp.

‹ The Index

Angular Signal Forms Migration

npm

MCP server that detects Angular Reactive Forms constructs and advises on migrating them to Angular Signal Forms (recipes verified against v22). Detect-and-advise only — never edits your code.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Install (Claude Code):

claude mcp add angular-signal-forms-migration -- npx -y angular-signal-forms-migration-mcp

tashan score: 48.0
Adoption: 38/wk
Upkeep: 62.0
Freshness: 92.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.5.2

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Angular Signal Forms Migration scores 48 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-angular-signal-forms-migration-mcp.svg)](https://tashan.sh/capability/pkg-angular-signal-forms-migration-mcp.html)

npm ↗ · source ↗ · pkg:angular-signal-forms-migration-mcp

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?