dragonflyoss/api

Canonical location of the Dragonfly API definition

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

dragonflyoss/api has 10+ stars and 20+ forks on GitHub, is written in Rust, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 8 minutes ago
Added to GitGenius on October 15th, 2026
Created on July 28th, 2022
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 21
Total Stargazers: 15 (+0)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.0 days
Mean response time: 11.0 days
90th percentile: 11.0 days
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • rust (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Dragonfly API is a canonical API definition repository that serves as the source of truth for Dragonfly service interfaces and their mocks.

The repository addresses the need for a centralized, authoritative location where API contracts for Dragonfly services are defined and maintained. It uses Protocol Buffers and gRPC to specify service interfaces, ensuring consistency across all components that depend on these APIs. By housing API definitions separately from implementation, the project enables multiple Dragonfly services to evolve independently while maintaining compatibility through a shared contract.

This repository is essential for anyone contributing to the Dragonfly ecosystem or building services that integrate with it. It suits projects that need to understand or extend Dragonfly's service interfaces. Developers who need to modify API definitions should coordinate with the Dragonfly maintainers through the established channels rather than making unilateral changes, as the API serves as a dependency for multiple downstream projects.

The project maintains active community engagement through multiple channels including Slack, GitHub Discussions, and developer mailing lists. Development follows a structured contribution process with clear guidelines documented in the repository's contributing documentation and code of conduct.