paperclipai/paperclip: technical due diligence, read from its repository

The median source file here is 103 lines. 233 files exceed 1,030 lines, the largest being 19,733. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

The suite is configured to retry failing tests (packages/paperclip-runner/src/drivers/codex/codex-question-adapter.test.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

The newest release, v2026.1012.0, is not on the branch this survey read; the newest release on it is v2026.1005.0. The shipped product may differ from what this report describes. Survey the release branch too.

8 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; 1 step pipes a download straight into a shell. 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.

21 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.

Third-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.

The newest was published on 2026-08-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 4 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 2026.1005.0. Answer lives in: the release you run, set against each fixed version. GHSA-265w-rf2w-cjh4 (high), GHSA-3xx2-mqjm-hg9x (critical), GHSA-47wq-cj9q-wpmp (critical) and 6 more are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 2 records name paperclip with nothing tying them to this repository (CVE-2015-2963, CVE-2017-0889).