infynon-pkg vs io.github.jmshinhwa/base-image-eol-lint
infynon-pkg is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
infynon-pkg is a plugin bundle for AI coding tools published by d4rkNinja. No marketplace we read lists it any more. io.github.jmshinhwa/base-image-eol-lint is an MCP server published by jmshinhwa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.jmshinhwa/base-image-eol-lint | |
|---|---|---|
| Community marketplace d4rkninja/code-guardian | Removed on 2026-10-20 Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (npm): 1 620 Downloads/week (npm): 0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | infynon-pkgno longer listed · | io.github.jmshinhwa/base-image-eol-lint |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | 1 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@readystack/base-image-eol-lint) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/d4rkninja/code-guardian | github.com/jmshinhwa/readystack-themes |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of infynon-pkg
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
-
OSV Dependency Vulnerability Check
Check npm, PyPI, Go and Maven packages or lockfiles against OSV.dev: CVEs, CVSS, fixed versions.
-
MCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs.
-
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
-
Query OSV.dev for known vulnerabilities by package and version, and scan lockfiles in batch.
-
Audit a dependency list for known vulnerabilities, licenses and outdated versions.
What each says it does
infynon-pkg
INFYNON Package Security Manager — Universal secure package installation, CVE scanning, auto-fix, dependency auditing, and vulnerability monitoring across 14 ecosystems
io.github.jmshinhwa/base-image-eol-lint
Marks every base image in your Dockerfiles, compose files and CI workflows whose security patches ha
How to run each
infynon-pkg
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.jmshinhwa/base-image-eol-lint As a local MCP server: npm package
claude mcp add --transport stdio base-image-eol-lint -- npx -y @readystack/base-image-eol-lint --mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: infynon-pkg · What it can do: io.github.jmshinhwa/base-image-eol-lint · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.