`Ghost CMS` Sites Hit by `ClickFix` Campaign via Critical CVE

// related

• #0001

  #0001Infra & SaaSAwesome MCP Servers10 hours ago

  `tickstem/mcp` added to `awesome-mcp-servers`

  40radar

  tickstem/mcpMCP server — monitoring and cron scheduling integration

  Uptime checks, heartbeat monitoring, and cron scheduling are now exposed through an MCP server. Useful if agent workflows need to inspect ops status or trigger scheduled jobs from one tool surface.

  • —tickstem/mcp covers uptime monitoring, heartbeat monitoring, and cron scheduling in one MCP integration.
  • —The fit is operational, not coding-specific: agents can read service health and schedule jobs without a separate dashboard hop.
  • —This is an index addition, not a product launch with pricing or benchmarks, so test scope stays limited.

  Source: github.com/punkpeye/awesome-mcp-servers/commit/08a3682d2Read original →
• #0002

  #0002Infra & SaaSGitHub Changelog14 hours ago

  `GitHub Code Quality` Adds Repository Enablement API

  50radar

  Repo-level quality checks can now be enabled and configured through API calls. Useful for automating setup across many repos, but it is still public preview.

  • —Repository Enablement API is available in public preview; avoid depending on it as a locked production contract yet.
  • —Two new endpoints support enabling and configuring GitHub Code Quality on individual repositories.
  • —Good fit for repo templates, onboarding scripts, and org-wide hygiene automation where manual settings drift quickly.

  Source: github.blog/changelog/2026-05-26-github-code-quality-repRead original →
• #0003

  #0003Infra & SaaSGitHub Changelogyesterday

  `GitHub` Adds PR Code Coverage Preview for Code Quality Users

  70radar

  Coverage now sits directly in the PR review loop. It reduces CI tab-hopping and makes test gaps harder to miss before merge.

  • —Available in public preview for all GitHub Code Quality users on github.com; coverage becomes part of normal PR review.
  • —PRs can show an aggregate covered-code percentage, so reviewers get a quick test-risk signal without opening separate reports.
  • —Best fit is repos already paying for GitHub Code Quality; teams outside that product get no immediate workflow change.

  Source: github.blog/changelog/2026-05-26-code-coverage-in-pull-rRead original →