balsam-flowPyPI
- latest 0.5.0
- last known licence BSD 3-Clause License
- stars 85
- assessment attempted 11 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 balsam-alcf/balsam, which is archived with a note saying development moved to argonne-lcf/balsam. 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
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — python >=3.6. Source: the registry.
- Open milestones — Launch web page 0/4 done. Source: the repository's milestones.
- OpenSSF Scorecard — 2.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 11 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-16 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/pypi/balsam-flow)
Watch it
Get told when balsam-flow 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.