Clojars
clojars.org · Storage · 1 record · JSON
Clojars (repo.clojars.org) Storage
fails: quotacountry-phoneno cardphoneRper-object-cap
| Free tier | No published byte quota on the site pages read. A 2020-era project commit records an 81 MB uberjar being rejected as 'too large for clojars', and a later commit adds a client-side 'uberjar size guard' - so there is a per-artifact ceiling in the tens-of-MB, historically around 100 MB. unit MB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Per-object cap | per-object-cap: ~100 MB (100000000 bytes) |
| Retention | per-object-cap: ~100 MB, from third-party evidence only (81 MB jar rejected). retention: indefinite (Maven-layout artifacts are immutable once deployed) |
| Egress | Free. repo.clojars.org is S3/CloudFront-backed ('Server: ... NoSuchKey' XML errors expose S3 origin) and serves without metering. |
| Identity | country-phone derived from the record's prose, not from an identity field, and no signup was executed: n the site pages read. A 2020-era project commit records an 81 MB uberjar being rejected as 'too large for clojars', and a later commit adds a client-side 'uberjar size guard' - so t |
| Limits |
per-object-cap: ~100 MB, from third-party evidence only (81 MB jar rejected). retention: indefinite (Maven-layout artifacts are immutable once deployed). request-rate: not documented. Write path is authenticated lein deploy with a Clojars token. |
| Binding | per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota |
| Interface | rest, rclone rest |
| Tooling | lein deploy clojars, clj -T:build deploy / deps-deploy, mvn deploy with the clojars repo, and plain HTTPS/Maven layout GETs. No rclone backend. |
| Composes with | unlimited artifacts (group/artifact/version) x unlimited versions x unlimited Clojars accounts (signup with an SSH key, free). At ~100 MB/artifact that is 100 MB x N; 20 TiB would need ~200,000 artifacts. Trivially repeatable in principle, brutally inefficient. |
| Reliability | Read path serves real jars (verified 3,224 and 16,324 bytes on real artifacts). The cap is the story and it is poorly documented - the only hard numbers come from a 2020 project commit and forum traffic. Confirming the current number would need an authenticated deploy probe. |
| Notes | No published byte quota on the site pages read. A 2020-era project commit records an 81 MB uberjar being rejected as 'too large for clojars', and a later commit adds a client-side 'uberjar size guard' - so there is a per-artifact ceiling in the tens-of-MB, historically around 100 MB. |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
| Parsed numbers |
|
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | repo.clojars.org/metosin/reitit/0.7.2/reitit-0.7.2.jar | probe: GET -> 200, 3,224 bytes |
| 2026-10-21 | repo.clojars.org/hiccup/hiccup/1.0.5/hiccup-1.0.5.jar | probe: GET -> 200, 16,324 bytes |
| 2026-10-21 | github.com/IntraCel/core/commit/568d4758f5994ac0aa4b7d015af7 | 'the uberjar task produced an 81MB jar file which was too large for clojars' |
| 2026-10-21 | github.com/pokle/clojr/commit/7c8b2b9b755f751b2f50cbe9e1fa97 | 'add uberjar size guard to deploy' |
More fields (1)
{
"dead_end": {
"failure_class": "quota",
"why": "No published byte quota on the site pages read. A 2020-era project commit records an 81 MB uberjar being rejected as 'too large for clojars', and a later commit adds a client-side 'uberjar size guard' - so there is a per-artifact ceiling in the tens-of-MB, historically around 100 MB.",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (7)
$.extras.dead_end.retry_whenprocess$.extras.dead_end.whypartly-held$.free_tier.notesprocess$.free_tier.statedpartly-held$.notespartly-held$.per_object_cap.notesnot-extracted$.retention.notesnot-extracted