Read 2026-10-04
luckypennysoftware/automapper: technical due diligence, read from its repository
What Borehole read in luckypennysoftware/automapper's code and history at 6e8697b: 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 | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE.md:1: The licence is a choice of RPL-1.5 or a commercial licenceLICENSE.txt: Relicensed: MIT → a choice of RPL-1.5 or a commercial licence (2025-07-02)
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.86 to 1.20 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.86, second half 1.20 (split 2017-11-14) |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate3 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/ci.yml:73 — action pinned by tag |
.github/workflows/lock.yml:19 — action pinned by tag |
The licence is a choice of RPL-1.5 or a commercial licence
adequateLICENSE.md grants a choice of RPL-1.5 or a commercial licence: open source; offering it over a network counts as distributing it, so a hosted product's changes must be published; deploying it, even for internal business use, obliges publishing the source of any changes and extensions. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE.md:1 — 10 lines, RPL-1.5 OR LicenseRef-Commercial |
Relicensed: MIT → a choice of RPL-1.5 or a commercial licence (2025-07-02)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.txt — MIT from 2011-07-03 |
LICENSE.md — a choice of RPL-1.5 or a commercial licence from 2025-07-02 |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-03-13. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-03-13: GHSA-rvv3-g6hj-g44x (high), fixed in 15.1.1: Denial of Service (DoS) via Uncontrolled Recursion |
Observability & Operations
not assessableNot rated: only 5 of 16 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 luckypennysoftware/automapper: 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.