github.com/taskcluster/json-eGo
- latest v3.0.2+incompatible
- licence MPL-2.0
- stars 212
- assessment attempted 7 days ago
- 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 →Moved
The registry still points at taskcluster/json-e, which is archived with a note saying development moved to json-e/json-e. The verdict above is about the new home.
Maintenance trends
Loading historical repository activity…
Signals · last 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
What the project says about itself
- Open milestones — Worker Lifecycle Management (due 2020-06-12); Postgres Phase 2 (due 2020-07-10). Source: the repository's milestones.
- OpenSSF Scorecard — 7.1 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 7 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-11 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/go/github.com/taskcluster/json-e)Watch it
Get told when github.com/taskcluster/json-e 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.