Code & Agentic RL · Consumer social (Android/iOS/PWA, backend, data eng, ML)

Multilingual Social-Media App Codebase (Full Org)

A full consumer social-media org: Android, iOS, PWA, backend, data engineering and ML, with 14 years of history.

CODE · 9 LANG · 388 REPOS · 4.2M LOC · 54M TOK
AvailabilityLead (metadata only)
388repos
4.2MLOC
285,870commits
Rights pending
01

Preview

Language mix (LOC)Illustrative
Java1.18M
Kotlin820K
JavaScript640K
Python520K
Swift410K
TypeScript300K
Elixir190K
C90K
Erlang50K

Shape only, pending the measured sheet. Ask for the counted distribution.

Preview · Language mix (LOC)
02

At a glance

Volume388 repos; 4.2M programming LOC / 54M tokens; 285,870 commits (2012-2026)
FormatsGit repos with history
LanguagesJava, C, Kotlin, JavaScript, Python, Elixir, Erlang, Swift, TypeScript
AnnotationMeasured code sheet
Licence statusRights pending
AvailabilityLead (metadata only)
Date addedOct 9, 2026
Update cadenceOne-off with history
Commits285,870
Tokens54M
03

Provenance ledger

Rights / consentPending
PII handlingScrub before preview
QA statusNot started
LicenceRights pending

No supplier, broker, client or personal names appear on this page or in its samples. Previews are Perit-owned copies with container metadata stripped.

Commits per year, 2012-2026
Repository shape, anonymised
org/
├── android-app/      312K LOC · Kotlin, Java
├── ios-app/          241K LOC · Swift
├── pwa/              188K LOC · TypeScript
├── feed-service/     96K LOC · Elixir
├── chat-gateway/     71K LOC · Erlang
├── ml-ranking/       64K LOC · Python
└── … 382 more repos
04

Schema and anonymised sample record

{
"repo_id": "PD-019-r007",
"primary_language": "Java",
"lines_of_code": 58214,
"commits": 4113,
"first_commit": "2016-04-02",
"last_commit": "2026-08-19",
"test_files": 212,
"ci_configured": true
}

The record above is synthetic: the field list and types are the real delivery schema, the values are not from the set. Full field documentation, including every optional column, ships with the pilot batch so you can write the loader before the data lands.

05

How delivery works. Four steps, and the first one is a request.

01 · Day 0RequestTell us the set, the use and the volume.
02 · 48 hoursSpec and quoteWritten spec, rights summary and price.
03 · 1-2 weeksPilot batchA QA'd slice in your data room to test against.
04 · OngoingDelivery to your bucketFull set or scheduled drops, same schema.
Access

Tell us the run, and we will tell you what clears for it.

Written spec, rights summary and price inside 48 hours, and a straight answer on anything still in review, including when the answer is that it will not clear.