Stroopwafel
C 65 completed
Library
unknown / clojure · tiny
14
Files
1,191
LOC
0
Frameworks
2
Languages
Pipeline State
completedRun ID
#300618Phase
doneProgress
1%Started
Finished
2026-04-13 01:31:02LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
41.64Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:40Deduplication group #50184
Member of a group with 6 similar repo(s) — canonical #24429 view group →
Top concepts (3)
testingLoggingTesting
Source: Repobility analyzer · https://repobility.com
AI Prompt
Create a project that implements capability-based authorization tokens specifically for Clojure. The system should build upon existing concepts like Biscuit and KEX. I need the core functionality to handle these tokens, potentially using CEDN for deterministic serialization, and the structure should be ready for development, including necessary documentation and testing setup.
clojure authorization security tokens biscuit kex web-security
Generated by gemma4:latest
Catalog Information
Stroopwafel provides capability-based authorization tokens for Clojure, building on Biscuit and KEX.
Description
Stroopwafel is a Clojure library that implements cryptographically signed, append-only authorization tokens with Datalog-based policy evaluation. It aims to bring the proof-of-concept from KEX to production quality while maintaining full feature parity with Biscuit. Stroopwafel uses CEDN for deterministic serialization.
الوصف
هو مكتبة لغة كلوچر تنفذ تذاكر إصدارات متتالية معقولة، مع تقييم سياسات البيان المنطقي. يهدف إلى جعل مفهوم KEX قابلًا للتشغيل في مستوى الإنتاج، بينما يحافظ على توافق الميزات الكاملة مع Biscuit. يستخدم Stroopwafel CEDN لتحديد التماثل.
Novelty
5/10Tags
authorization tokens policy-evaluation deterministic-serialization clojure-library capability-based-authentication
Claude Models
claude-opus-4.6
Quality Score
C
65.2/100
Structure
75
Code Quality
44
Documentation
47
Testing
70
Practices
78
Security
100
Dependencies
50
Strengths
- Good test coverage (60% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Good security practices \u2014 no major issues detected
- Properly licensed project
Weaknesses
- No CI/CD configuration \u2014 manual testing and deployment
- 1 files with critical complexity need refactoring
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
Security & Health
6.1h
Tech Debt (E)
High
DORA Rating
A
OWASP (100%)
PASS
Quality Gate
Repobility · MCP-ready · https://repobility.com
A
Risk (10)
EPL-2.0
License
1.7%
Duplication
Languages
Frameworks
None detected
Concepts (3)
| Category | Name | Description | Confidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Repobility · severity-and-effort ranking · https://repobility.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| arch_layer | testing | Detected testing layer | 70% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| business_logic | Logging | Detected from 2 related files | 50% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| business_logic | Testing | Detected from 3 related files | 50% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Embed Badge
Add to your README:
