# evergreen-deprecation

Find end-of-life and deprecated runtimes, packages, and GitHub Actions at exact file locations, with sources and migration context. CLI, MCP server, GitHub Action, Agent Skill.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.5.0
- **Author:** Unknown
- **License:** Apache-2.0
- **npm:** evergreen-deprecation
- **Source:** https://github.com/arminazimi/evergreen
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-22T07:30:22.458Z
- **Version scanned:** 0.5.0
- **CVEs:** none found by OSV at scan time

## Tools

6 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scan_repository` — Run all built-in Evergreen detectors against a local repository and return the complete versioned scan result.
- `list_deprecations` — Run a fresh local scan and return a compact, versioned list of lifecycle findings.
- `explain_deprecation` — Run a fresh local scan and return one complete evidence-backed finding by ID.
- `create_migration_context` — Create a validated, rule-specific migration packet for one finding from a fresh local scan.
- `verify_migration` — Re-scan locally and check whether a finding observed earlier in this MCP session is gone. Suggested project commands are returned but never executed.
- `check_dependency` — Check one package, and optionally one version, against Evergreen's lifecycle rules before adding it to a project. Pass a Package URL such as pkg:npm/request@2.8

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"evergreen-deprecation\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"evergreen-deprecation\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 12, ceiling 30 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/evergreen-deprecation
- Install plan: https://forgeregistry.com/api/v1/packages/evergreen-deprecation/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/evergreen-deprecation
- HTML page: https://forgeregistry.com/registry/evergreen-deprecation
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.