Read 2026-09-26
pallets/itsdangerous: technical due diligence, read from its repository
What Borehole read in pallets/itsdangerous's code and history at 672971d: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | not assessable |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- No release for 14 months while development continues
Architecture & Codebase — including AI provenance
not assessableNot rated: only 5 of 11 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 115 absorb 31% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
requirements/dev.txt — 86 commits touched it |
itsdangerous.py — 67 commits touched it |
.pre-commit-config.yaml — 63 commits touched it |
.github/workflows/tests.yaml — 52 commits touched it |
requirements/tests.txt — 37 commits touched it |
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.30 to 0.90 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.30, second half 0.90 (split 2018-06-19) |
No release for 14 months while development continues
adequateThe last tag, 2.1.x, is 423 days older than the newest commit; the typical gap between releases was 16 days, and 16 commits landed in the last 90 days. Users run the last release, not this code.
| last tag 2.1.x |
Security & Reliability Posture
adequate11 locked dependencies have published vulnerabilities, 8 high or critical
adequate11 of 68 locked dependencies match 29 published advisories in OSV, 8 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Observability & Operations
not assessableNot rated: only 4 of 15 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on pallets/itsdangerous: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.