Clj Midas
C 66 completed
Other
api / clojure · tiny
19
Files
1,514
LOC
0
Frameworks
5
Languages
Pipeline State
completedRun ID
#1357045Phase
doneProgress
0%Started
2026-04-16 03:02:49Finished
2026-04-16 03:02:49LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
46.71Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:34Deduplication group #54475
Member of a group with 1 similar repo(s) — this repo is canonical view group →
Source: Repobility analyzer · https://repobility.com
AI Prompt
Create a Clojure client library that interacts with the California Energy Commission's MIDAS API. I need it to be spec-driven, using an OpenAPI spec as the single source of truth, and built on Martian. Key features should include handling rate data, GHG emissions signals, Flex Alerts, and utility holidays. Please implement auto-refreshing authentication for 10-minute bearer tokens. The library must support a two-layer data model: raw API responses and coerced Clojure entities, and it should use Malli schemas for validation. Include functions to list RINs, fetch rate values, and get utility holidays.
clojure api-client energy midas openapi http-client data-modeling
Generated by gemma4:latest
Catalog Information
Create a Clojure client library that interacts with the California Energy Commission's MIDAS API. I need it to be spec-driven, using an OpenAPI spec as the single source of truth, and built on Martian. Key features should include handling rate data, GHG emissions signals, Flex Alerts, and utility holidays. Please implement auto-refreshing authentication for 10-minute bearer tokens. The library must support a two-layer data model: raw API responses and coerced Clojure entities, and it should use
Tags
clojure api-client energy midas openapi http-client data-modeling
Quality Score
C
66.2/100
Structure
69
Code Quality
63
Documentation
37
Testing
70
Practices
75
Security
92
Dependencies
50
Strengths
- Good test coverage (50% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No CI/CD configuration — manual testing and deployment
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
