@accordproject/markdown-commonnpm
- latest 1.1.0
- last known licence Apache-2.0
- stars 86
- assessment attempted 12 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 →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
- Build provenance — the latest release, 1.1.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=22. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Open milestones — Implement image; Implement optional (due 2021-08-05) 1/1 done; Implement conditonal (due 2021-08-05) 1/1 done; Implement formula (due 2021-08-10) 1/1 done; Implement list (due 2021-08-17). Source: the repository's milestones.
- OpenSSF Scorecard — 4.3 / 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 12 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/npm/@accordproject/markdown-common)Watch it
Get told when @accordproject/markdown-common 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.