@crouter/env-dockernpm

Verdict

Looks abandoned

@crouter/env-docker appears abandoned. No issue data available. Plan a migration rather than waiting for a fix.

health 10/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

registry marks the package deprecated

Judged yesterday from signal heuristics. How each verdict is decided

latest 0.3.409
last known licence GPL-3.0-only
assessment attempted yesterday
registry checked yesterday
registry ↗
repository ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

—

Open issues

—

Unanswered

—

Contributors

—

What the project says about itself

Build provenance — the latest release carries no provenance attestation. Source: the registry.
Publishers on the registry — 1. Source: the registry.

Third-party facts checked 21 days ago; registry facts on every crawl.

State history 2

When	Change
2026-10-28	active → abandoned
2026-10-09	first verdict: active

Where to go instead 1

@north-light/env-docker

Named by the maintainers in the deprecation notice

Moved to @north-light/env-docker: npm install -g @north-light/env-docker (this package is no longer maintained)

From the maintainers’ own deprecation notice.

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@crouter/env-docker.svg)](https://isitdeadyet.dev/npm/@crouter/env-docker)

Watch it

Get told when @crouter/env-docker changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.