jbaruch/pidge
Context tile for pidge notification library v3 - async API with NotificationClient, Message, and dispatch pattern
99
Quality
99%
Does it follow best practices?
Impact
100%
2.85xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
79%Order Confirmation Notification Endpoint
Async notification dispatch endpoint
Async context manager
0%
100%
NotificationConfig from env
70%
100%
Message keyword arguments
50%
100%
Uses dispatch not send
0%
100%
Delivery confirmation check
0%
100%
Logs message_id
0%
100%
DispatchError caught explicitly
0%
100%
No 500 on DispatchError
100%
100%
notification_sent in response
0%
100%
No v2 API usage
0%
100%
100%
50%Resilient Password Reset Notification Service
Retry logic with exponential backoff
Retry up to 3 attempts
100%
100%
Exponential backoff sleep
100%
100%
asyncio.sleep for backoff
100%
100%
No retry on permanent errors
100%
100%
DispatchError caught
0%
100%
Logs failure after retries
100%
100%
Async context manager lifecycle
0%
100%
Result check after success
0%
100%
Logs message_id on success
0%
100%
notification_sent in response
0%
100%
100%
66%Upgrade Legacy Notification Code to Current Library Version
v2 to v3 migration
No Notifier class
100%
100%
No NotifierConfig class
100%
100%
No .send() method
100%
100%
Uses NotificationClient
0%
100%
Uses NotificationConfig
0%
100%
Async context manager
0%
100%
API key from env
0%
100%
Message keyword args
0%
100%
Delivery result check
0%
100%
DispatchError handling
0%
100%
notification_sent field
50%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6