yangzongzhuan/RuoYi-Vue

:tada: (RuoYi)官方仓库 基于SpringBoot,Spring Security,JWT,Vue & Element 的前后端分离权限管理系统,同时提供了 Vue3 的版本

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 21st, 2026
Created on November 7th, 2019
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 1,704
Total Stargazers: 3,219 (+0)
Total Subscribers: 43 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 63.2 days
Mean response time: 97.2 days
90th percentile: 240.0 days
Tracked items: 11

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 346 days
Stale 30+ days: 10
Stale 90+ days: 7

Recent activity

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

Top labels

  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

RuoYi-Vue is a front-end and back-end separated permission management system built with Spring Boot, Spring Security, JWT, Vue, and Element UI.

The system addresses the need for a comprehensive role-based access control platform by combining a Java backend with a Vue-based frontend. The architecture separates concerns between client and server, with the backend handling authentication through JWT tokens and Spring Security, while the frontend provides an Element UI-based administrative interface. The system includes support for role and permission management, allowing fine-grained control over user access to features and data.

Organizations building internal admin dashboards or management systems should consider this tool if they are already invested in the Spring Boot and Vue ecosystems. The project suits teams that need a ready-made foundation for permission management rather than building these systems from scratch. It provides both Vue 2 and Vue 3 versions, allowing teams to choose based on their modernization timeline and existing codebase compatibility.

Development activity shows consistent engagement with the codebase. The project maintains regular updates to address issues and incorporate improvements. There is active community participation through issue tracking and pull requests. The maintainers respond to user feedback and contribute directly to the repository's evolution. Documentation is actively maintained to reflect current functionality and usage patterns.