Borehole · Project · free tier
getpelican/pelican
Free reading: not for reliance
c2fff53 · 4,034 commits · 480 files
Read 2026-11-03

getpelican/pelican: technical due diligence, read from its repository

What Borehole read in getpelican/pelican's code and history at c2fff53: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.5

Effort is shifting from building to rewriting

adequate

Deleted lines per line added rose from 0.62 to 0.80 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.

Evidence
first half 0.62, second half 0.80 (split 2018-09-13)

Security & Reliability Posture

strong
05.27

The build runs third-party code it does not pin

adequate

4 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.

Evidence
.github/workflows/main.yml:32 — action pinned by tag
.github/workflows/main.yml:51 — action pinned by tag
05.22

1 deserialiser that can run code

adequate

1 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

Evidence
pelican/cache.py:36 — code-executing deserialiser

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on getpelican/pelican: 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.