python-poetry / poetry
Repository health
Security advisories, maintenance activity, dependencies and license for python-poetry/poetry, with what was checked and what was not.
Security
74 dependencies checked (24 direct), pypi, via deps.dev. Findings apply only to the packages and versions checked.
OpenSSF Scorecard · 3.1/10
Checks sorted from strongest to weakest.
- Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 1010/10
- Pinned-Dependenciesall dependencies are pinned10/10
- Licenselicense file detected10/10
- Packagingpackaging workflow detected10/10
- Code-ReviewFound 21/29 approved changesets -- score normalized to 77/10
- Branch-Protectionbranch protection is not maximal on development and all release branches1/10
- Dangerous-Workflowdangerous workflow patterns detected0/10
- Token-Permissionsdetected GitHub workflow tokens with excessive permissions0/10
- Binary-Artifactsbinaries present in source code0/10
- CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected0/10
- Security-Policysecurity policy file not detected0/10
- Fuzzingproject is not fuzzed0/10
- Signed-ReleasesProject has not signed or included provenance with any releases.0/10
- SASTSAST tool is not run on all commits -- score normalized to 00/10
Maintenance
Outside contributions: 17 of 50 external pull requests merged (63% of those decided), median 5.2 days to merge.From the 98 most recently updated pull requests, bots excluded.
Commit activity
100 commits sampledClick a bar to browse commits — or open GitHub for the full month ↓
Work rhythm
Commits by day of week
Pull request health
How fast do PRs resolve?
Days from open to merged / closed, last 13 PRs.
Pending right now17 open PRs
![pre-commit-ci[bot]](https://avatars.githubusercontent.com/in/68672?v=4)
Recently merged10 PRs in the recent window
Issue triage — last 12 weeks
Blue bars = issues opened that week, green = closed. Healthy projects keep these roughly in balance — a persistently bigger blue bar means an opening backlog. open issues on GitHub ↗
Release cadence· median 14d between releases
Latest 2.5.1 shipped 25d ago · typical gap 14d · shipping faster than before · 10 releases sampled.
New faces — last 90 days28 contributors appearing for the first time in this window
Heuristic: contributors whose earliest commit in the recent sample is < 90 days old AND who have ≤ 3 commits in the window. Click a name for their commits in this repo.
Top contributors
Issue health
Computed from GitHub Issues — no estimates. Per-issue rates use the 24 most-recently-updated issues (recent, not all-time); the open total and oldest-open age are repo-wide.
Total open on the repo (authoritative).
From 15 recently-closed issues. p90 6.2y.
Age of the longest-open unresolved issue.
0 of 9 recent open issues have no comments yet.
0 of 9 recent open issues had no update in 30d+.
0 of 9 recent open issues are unlabeled.
What the backlog is about
AI-generatedOpen issues grouped into themes by an LLM from their titles — a summary, not an authoritative classification. Numbers reflect the 9 most-recently-active open issues.
Most-wanted
Open issues with the most positive reactions — what the community is asking for.
Activate `requires-plugins` from a project without using `poetry install`
#9990 · opened 1y ago · @tungol
group-specific updates to extras work: unintended, or undocumented?
#8581 · opened 3y ago · @a-recknagel
Parallel installs can fail to resolve setuptools due to a SeparateBodyFileCache race
#11048 · opened 1mo ago · @igormishsky
Most-discussed
Open issues with the most comments — where the conversation is.
Activate `requires-plugins` from a project without using `poetry install`
#9990 · opened 1y ago · @tungol
`poetry add` with `||` operator breaks further poetry commands
#10569 · opened 1y ago · @rzuckerm
group-specific updates to extras work: unintended, or undocumented?
#8581 · opened 3y ago · @a-recknagel
Bug on poetry install `ValueError: invalid literal for int() with base 10: ''`
#10963 · opened 3mo ago · @MarcBresson
Parallel installs can fail to resolve setuptools due to a SeparateBodyFileCache race
#11048 · opened 1mo ago · @igormishsky
Labels in the recent sample
Per-issue rates are computed from a sample of 24 most-recently-updated issues, so they describe recent behavior rather than the all-time backlog. Reaction and comment counts come straight from GitHub.
Dependencies
Checked packages and import counts
Checked counts describe advisory coverage, not the repository’s complete dependency inventory. External imports come from a separate source-code graph.