Skip to content

Clojars (repo.clojars.org)

clojars.orgRegistrystorage/clojarsJSON compare report an error provider JSON

Free allowance: No published byte quota on the site pages read.
Verdict: fails: quotathe free allowance is too small to matter
Cost: free tier
Identity: country-phone?placeholder, not evidence; card unknown, phone unknown
Binding limit: per-object-capper-object-cap: ~100 MB
Evidence: reported4 sources; a third party said so
Freshness: stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05

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
Limits	per-object-cap (binding) per-object-cap: ~100 MB source 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.
Identity	country-phone (inferred, not read) not published
Egress	Free. repo.clojars.org is S3/CloudFront-backed ('Server: ... NoSuchKey' XML errors expose S3 origin) and serves without metering.
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)
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.
Parsed numbers	has-free-tier 1 per-object-cap 100 MB

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 values 2

per object cap notes: the field may be stated in a source that was not read
retention notes: the field may be stated in a source that was not read