azure/bicep

Bicep is a declarative language for describing and deploying Azure resources

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 19th, 2026
Created on May 13th, 2020
Open Issues & Pull Requests: 1,061 (+0)
GitHub issues: Enabled
Number of forks: 830
Total Stargazers: 3,645 (+0)
Total Subscribers: 107 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 41.0 hours
Mean response time: 114.1 days
90th percentile: 199.0 days
Tracked items: 1,229

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 83% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Needs: Triage :mag:" is answered fastest, typically in about 9 hours, while "Quality Sprint" waits about 2 weeks. 65% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. 76% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 362
New in 7 days: 3
Closed in 7 days: 6
Avg open age: 920 days
Stale 30+ days: 336
Stale 90+ days: 292

Recent activity

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

Top labels

  • enhancement (421)
  • Needs: Triage :mag: (342)
  • bug (128)
  • Needs: Upvote (120)
  • Quality Sprint (106)
  • devdiv (104)
  • code-formatting-automation (85)
  • story: bicep parameters (65)

Detailed Description

Bicep is a declarative infrastructure-as-code language for describing and deploying Azure resources. It provides a more concise and readable syntax compared to traditional Azure Resource Manager templates, with the language service integrated into tooling like the VS Code extension.

Bicep addresses the complexity of writing and maintaining Azure infrastructure definitions by offering a cleaner declarative syntax that reduces verbosity. The approach works by allowing developers to author Bicep files using language services in VS Code, then transpiling that code to ARM templates automatically. Both Azure CLI and PowerShell Az module have built-in Bicep support, so standard deployment commands work directly with .bicep files without manual compilation steps. For teams with existing ARM templates, Bicep provides decompilation capabilities to convert legacy templates into the new format.

Bicep suits organizations already committed to Azure who want to simplify their infrastructure-as-code workflows. It is particularly valuable for teams managing multiple deployments that benefit from consistent, repeatable infrastructure definitions. The project provides a migration path for existing ARM template users through decompilation tooling. A rich ecosystem of pre-built modules exists through Azure Verified Modules and the azure-quickstart-templates repository, along with a browser-based playground for experimentation.

The project maintains active development with regular updates to language features and tooling. The codebase shows consistent engagement across multiple areas including the language compiler, VS Code extension, and documentation. Pull requests receive timely review and integration. The project sustains a comprehensive test suite covering language functionality and edge cases. Documentation is kept current alongside feature development, with learning paths and migration guides available to support adoption.