admet-workbenchPyPI
- latest 0.1.1
- last known licence MIT
- stars 57
- assessment attempted 26 days ago
- GitHub evidence observed 26 days ago
- registry checked 28 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 2 checks
Commits 90d
100
Open issues
192
Unanswered
177
Contributors
1
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — python >=3.10. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Workbench 0.9.0 (due 2025-11-30) 62/89 done; Compound Explorer v0 (due 2026-01-01) 2/17 done; Workbench: 0.9.x (due 2026-02-28) 1/27 done; Workbench: 0.10.0 (due 2026-04-30) 0/63 done; Future (due 2026-07-31) 0/58 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.8 / 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 26 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-21 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/admet-workbench)
Watch it
Get told when admet-workbench 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.