pypa/pipenv vs python-poetry/poetry
Both showing Healthy signals — pick on fit, not health
As of September 2026, pipenv and poetry both show healthy maintenance signals. pipenv was committed to 3 weeks ago with 4+ active contributors, while poetry was committed to 2 days ago with 33+ active contributors. Both use the MIT license. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
pypa/pipenv
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Small team — 4 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 93% of recent commits
- ✓Last commit 3w ago
- ✓4 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
python-poetry/poetry
Strong maintenance signals
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 1/10; Scorecard "Token-Permissions" is 0/10
- ⚠Scorecard: dangerous CI workflow (0/10)
- ⚠Scorecard: default branch unprotected (1/10)
- ✓Last commit 1d ago
- ✓33+ active contributors
- ✓Distributed ownership (top contributor 43% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| pipenv | poetry | |
|---|---|---|
| Stars | 25,032 | 34,303 |
| Last commit | 23d ago | 2d ago |
| License | MIT | MIT |
| Open issues | 14 | 571 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 25% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? pypa/pipenv · python-poetry/poetry
Ask AI about pypa/pipenv vs python-poetry/poetry
Open the chat with a comparison question pre-filled.