Enterprise DNAEnterprise DNA

Skills

traefik-route-manager

by jae-jae

Web UI for managing Traefik File Provider dynamic routes

Our verdict

Not reviewed yet

We have not reviewed traefik-route-manager yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About traefik-route-manager

A web interface for managing Traefik File Provider dynamic routes. It lets users view, add, edit, and remove routes through a browser, with changes written to the File Provider configuration.

Best for

Developers or small teams who prefer a GUI over editing Traefik YAML files directly

Use cases

  • Add or update Traefik routes without editing YAML files manually
  • Remove obsolete or unused routes to keep the routing config clean
  • Review existing route definitions in a visual dashboard

Notes

34 stars on GitHub. Last updated 2026-03-30.

Pros

  • Simplifies route management for teams unfamiliar with Traefik config syntax
  • Uses the File Provider, so changes can be version-controlled
  • Open source with a small, focused codebase in TypeScript

Cons

  • Low adoption (34 stars) may indicate limited community support or maturity
  • Requires running and securing an additional web service
  • Assumes File Provider usage, not suitable for other providers like Consul or etcd

Key facts

What we have checked

Days since the last commit
229
Checked GitHub
GitHub forks
3
Checked GitHub
GitHub stars
34
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How traefik-route-manager is growing

GitHub stars

34 to 34

stars. 1 Nov 2026 to 14 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is traefik-route-manager looked after, and what do its setup files show

Health score

20 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity12.2 of 30Last push 229 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Security check static checks

40 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-skill-static-v1 main@1fabec145bc3. What it checks

  • High Browserslist: Uncaught crash / prototype write via untrusted browserslist-stats.json custom stats (normalizeStats) (affects browserslist 4.28.1, pinned in web/package-lock.json).
  • High Browserslist: Unbounded memory growth (no cache eviction) via distinct query results, leading to eventual OOM (affects browserslist 4.28.1, pinned in web/package-lock.json).
  • High nanoid: non-secure generators can loop indefinitely with negative size (affects nanoid 3.3.11, pinned in web/package-lock.json).
  • High nanoid: custom generators can loop indefinitely when size is zero (affects nanoid 3.3.11, pinned in web/package-lock.json).
  • High nanoid: Integer Overflow or Wraparound (affects nanoid 3.3.11, pinned in web/package-lock.json).
  • High PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments (affects postcss 8.5.8, pinned in web/package-lock.json).
  • High PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure (affects postcss 8.5.8, pinned in web/package-lock.json).
  • High source-map-js allows event-loop denial of service through indexed source-map section offsets (affects source-map-js 1.2.1, pinned in web/package-lock.json).
  • High launch-editor: `fs.existsSync()` existence check can be bypassed on Windows (affects vite 6.4.1, pinned in web/package-lock.json).
  • High vite: `server.fs.deny` bypass on Windows alternate paths (affects vite 6.4.1, pinned in web/package-lock.json).
  • High Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket (affects vite 6.4.1, pinned in web/package-lock.json).
  • Medium baseline-browser-mapping process termination on invalid input causes denial of service (affects baseline-browser-mapping 2.10.11, pinned in web/package-lock.json).
  • Medium PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion (affects postcss-selector-parser 6.1.2, pinned in web/package-lock.json).
  • Medium PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset (affects postcss 8.5.8, pinned in web/package-lock.json).
  • Medium PostCSS has XSS via Unescaped </style> in its CSS Stringify Output (affects postcss 8.5.8, pinned in web/package-lock.json).
  • Medium Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling (affects vite 6.4.1, pinned in web/package-lock.json).
  • Medium launch-editor: escapeCmdArgs() omits % escaping on Windows (affects vite 6.4.1, pinned in web/package-lock.json).
  • Medium launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors (affects vite 6.4.1, pinned in web/package-lock.json).
  • Medium Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine (affects vite 6.4.1, pinned in web/package-lock.json).
  • Medium launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows (affects vite 6.4.1, pinned in web/package-lock.json).
  • Low @babel/core: Arbitrary File Read via sourceMappingURL Comment (affects @babel/core 7.29.0, pinned in web/package-lock.json).
  • Low postcss-selector-parser allows denial of service through uncontrolled AST recursion (affects postcss-selector-parser 6.1.2, pinned in web/package-lock.json).
  • Low Vite: Cross origin script execution through Vite custom middleware (affects vite 6.4.1, pinned in web/package-lock.json).

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

  1. Security finding

    Source: osv.dev

  2. Security finding

    Source: osv.dev

  3. Security finding

    Source: osv.dev

  4. Security finding

    Source: osv.dev

  5. Security finding

    Source: osv.dev

  6. Security finding

    Source: osv.dev

  7. Security finding

    Source: osv.dev

  8. Security finding

    Source: osv.dev

  9. Security finding

    Source: osv.dev

  10. Security finding

    Source: osv.dev

  11. Security finding

    Source: osv.dev

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.