@azure-tools/typespec-foundry-corenpm
- latest 0.1.0-dev.2
- last known licence MIT
- stars 3,104
- assessment attempted 18 days ago
- GitHub evidence observed 18 days ago
- registry checked 9 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 carries no provenance attestation. Source: the registry.
- Supported runtime — node >=24.14.1. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Sprint-118 2/2 done; June 4/5 done; GA 2/2 done; Sprint 155 (due 2019-07-12); Sprint 156 (due 2019-08-02) 0/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 7.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 18 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-19 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@azure-tools/typespec-foundry-core)Watch it
Get told when @azure-tools/typespec-foundry-core 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.