Oci
C+ 71 completed
Other
unknown / elixir · tiny
35
Files
3,435
LOC
0
Frameworks
3
Languages
Pipeline State
completedRun ID
#1487540Phase
doneProgress
0%Started
2026-04-16 11:48:54Finished
2026-04-16 11:48:54LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
22.69Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #47886
Member of a group with 70 similar repo(s) — canonical #1494485 view group →
Repobility — same analyzer, your code, free for public repos · /scan/
AI Prompt
Create an OCI compliant V2 registry server implementation using Elixir. I need a library that can be plugged into an existing Phoenix application. The system must support pluggable storage backends and configurable authentication. Key features to include are full OCI Distribution Specification V2 compliance, support for Docker and OCI image formats, and compatibility with the Docker CLI and ORAS tools. It should also handle standard OCI repository naming conventions like `namespace/name` and `org/team/project`.
elixir phoenix oci registry container v2 storage api
Generated by gemma4:latest
Catalog Information
Create an OCI compliant V2 registry server implementation using Elixir. I need a library that can be plugged into an existing Phoenix application. The system must support pluggable storage backends and configurable authentication. Key features to include are full OCI Distribution Specification V2 compliance, support for Docker and OCI image formats, and compatibility with the Docker CLI and ORAS tools. It should also handle standard OCI repository naming conventions like namespace/name and `or
Tags
elixir phoenix oci registry container v2 storage api
Quality Score
C+
70.7/100
Structure
75
Code Quality
59
Documentation
63
Testing
75
Practices
74
Security
90
Dependencies
50
Strengths
- CI/CD pipeline configured (github_actions)
- Good test coverage (42% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Properly licensed project
Weaknesses
- Potential hardcoded secrets in 1 files
- 344 duplicate lines detected — consider DRY refactoring
Recommendations
- Add a linter configuration to enforce code style consistency
- Move hardcoded secrets to environment variables or a secrets manager
Languages
Frameworks
None detected
Embed Badge
Add to your README:
