This repository provides a full-stack demonstration of a permission management system using Spring Boot for the backend and Vue.js for the frontend. Despite its name, it does not use Apache Shiro; instead, it implements a custom, annotation-based permission control via AOP (RequiresPermissions annotation and PermissionAspect) and token-based authentication using Caffeine local cache. The backend is a monolithic Spring Boot 2.3.10 application with MyBatis for database access, serving a REST API. The frontend is a Vue 2 application (based on vueAdmin-template) with dynamic routing and ElementUI, featuring a custom directive for button-level permission checks. The system supports multi-role users, role-based menu and permission assignment, and a clean separation of concerns between backend and frontend permission enforcement. The codebase is well-structured and serves as a clear reference for implementing RBAC-like permission systems in Java+Vue projects, though it is not intended for production use without significant hardening and updates.
LiteOps is a lightweight, self-hosted CI/CD platform built with Django 4.2 (Python 3.9) and Vue 3 (Ant Design Vue). It provides project management, build task configuration, credential storage (GitLab tokens, SSH keys, kubeconfig), environment management, and notification robots (DingTalk, WeChat, Feishu). Builds are executed inside a Docker-in-Docker container that includes Java, Maven, Node, and kubectl, with real-time log streaming via Server-Sent Events (SSE). The system integrates with GitLab for webhook-triggered builds and branch/commit information, supports LDAP authentication, and enforces role-based permissions (function and data scopes). The frontend dashboard displays build statistics, trends, and recent builds using ECharts. The codebase is functional and actively developed, but exhibits several engineering weaknesses: no automated tests, threading for async build execution (no task queue), hardcoded secrets (admin password, database credentials), SHA256 password hashing (not bcrypt), and plaintext storage of GitLab tokens. The Docker image is large and requires privileged mode. Despite these issues, the system is suitable for small teams needing a simple, integrated CI/CD solution without external dependencies beyond GitLab and MySQL.
PutongOJ is a full-stack online judge platform built as a pnpm monorepo with TypeScript across the stack. The backend is a Koa 3 server using MongoDB (Mongoose) and Redis, with a separate judger component that executes submissions in a privileged Docker sandbox via go-judge. The frontend is a Vue 3 application using PrimeVue, Pinia, and Vue Router; it provides problem CRUD, testcase management, contest ranklists/status, course management, discussions, and account settings. A shared package (@putong-oj/shared) contains Zod schemas and enums used by both server and client. Although primarily an application, it includes a data migration subsystem and a documented testcase data format, giving it a minor data-engineering flavor.
LiveAutoRecord is a multi-platform live stream recording application built on a TypeScript monorepo architecture. It supports three distinct deployment modes: a desktop client (Electron), a headless HTTP server (Express), and a CLI tool. The core functionality revolves around automatically detecting live streams from platforms like Bilibili, Douyu, Huya, and Douyin, resolving stream URLs, and capturing video via FFmpeg while simultaneously collecting metadata such as danmu and gift messages. The system uses a provider pattern to allow extensibility for new platforms. The architecture relies heavily on Node.js 22+ and Electron 40, indicating a commitment to bleeding-edge runtime versions. Data persistence is handled via LowDB with JSON file adapters, which serves the application's needs but introduces scalability limitations for large datasets. The codebase demonstrates solid engineering practices in its separation of concerns, with distinct packages for core logic, platform-specific adapters, and shared utilities. However, the reliance on platform-specific anti-crawl logic (e.g., VM execution for Huya, signature generation for Douyu) creates inherent fragility. A critical technical debt issue is the use of the `vm2` library in the Douyu recorder, which carries known critical security vulnerabilities (CVE-2023-37466). While a replacement plan exists in the documentation, the current state poses a significant security risk. Additionally, the high number of open issues (89) relative to the star count suggests accumulating technical debt and feature requests that may impact long-term stability.
This repository is a comprehensive AI inference and application platform built primarily on Java (Spring Boot) and Vue.js. It provides a suite of SDKs for computer vision (face recognition, OCR, segmentation), NLP (text embedding, translation), and AIGC (Stable Diffusion, ControlNet). The architecture is modular, separating inference logic (SDKs) from application logic (Web Apps, Desktop Apps, API Platform). It utilizes Deep Java Library (DJL) for model inference, integrating PyTorch and ONNX Runtime backends. The system supports multimodal search (Face, Image, Code, Text) using vector databases like Milvus. Hybridity: While it contains AI research components (models, inference), the codebase is structured as a production-ready software platform with web interfaces, APIs, and desktop wrappers, rather than a research notebook collection. It functions as a monorepo containing multiple distinct Spring Boot applications and Vue.js frontends, each serving a specific AI task (e.g., face_search, image_search, aigc_image_gen).
AntMgr is an ASP.NET Core MVC admin management framework designed for rapid development of backend systems. It provides built-in user, role, menu, and permission management with button-level authorization, along with a CRUD code generator and a SQL query tool. The architecture follows a layered pattern: Web (mgr.core) -> ServicesModel -> ViewModels -> Repository -> Infrastructure, using Autofac for DI, AutoMapper for object mapping, and a custom ORM (AntData.ORM) supporting MySQL and SQL Server. The frontend relies on jQuery, Bootstrap 3, and Vue.js 1.0 with numerous third-party plugins for UI components. Key features include role-based access control with hierarchical roles and god-mode bypass, a code generation engine using DotLiquid templates that produces full CRUD modules (Controller, Repository, ViewModel, ServiceModel, View), Excel import/export via Npoi.Mapper, and an integrated SQL editor with field hints. The system emphasizes convention over configuration, allowing developers to quickly scaffold admin pages with minimal setup. While functionally complete and actively maintained (last commit 2026-03-16), the codebase carries significant technical debt from outdated frontend libraries (Vue 1.0, Bootstrap 3, numerous jQuery plugins from 2014-2016) and a custom ORM that may lack community support. The hardcoded god-mode users and direct SQL execution tool also pose security risks. The code generation engine and Excel helper are the most reusable components, demonstrating practical patterns for meta-programming and data I/O.
This repository is a Vue 3 admin dashboard template (vue3-admin-better) built with Element Plus, Vuex, Vue Router, and Rspack as the build tool. It provides a full-featured management system UI with login, registration, error pages, and over 40 demo CRUD pages for common business modules like projects, teams, tasks, customers, knowledge base, and workflows. The architecture follows a standard SPA pattern with dynamic routing based on RBAC permissions (intelligence/all modes), multiple layout variations (vertical/horizontal), theme customization (three themes persisted to localStorage), and a mock API layer using MockJS. Key entry points include `src/main.js` (app bootstrap), `src/layouts/index.vue` (main layout container), and `src/router/index.js` (route definitions). The state management uses Vuex with modules for user, routes, settings, tabs, and error logs. External dependencies include Vue 3, Element Plus, ECharts, Axios, and vuedraggable. The codebase demonstrates typical admin template patterns but has several maintenance and security concerns: mock interceptors are forced in production (a serious risk), a local `layouts` package dependency, fragile FontAwesome-to-Element-Plus icon mapping, and hardcoded mock data with no real backend integration. These issues limit direct production readiness without significant refactoring.
Cube UI is a Vue.js 2.x-based mobile UI component library providing reusable components for building mobile/web applications. It offers a comprehensive set of touch-optimized UI elements including buttons, forms, pickers, popups, drawers, and layout components. The library follows Vue plugin patterns with installable components and supports both declarative template usage and programmatic invocation via a create-api pattern. It includes internationalization support, form validation, and integrates with better-scroll for advanced scrolling components. The repository contains source code, build outputs, documentation, examples, and unit tests.
The Kalendar repository is a Vue 2 plugin that provides a flexible calendar component for managing events. It features week and day views, drag-and-drop event creation, customizable slots for event rendering, and configuration options for appearance and behavior. The component leverages web workers to offload heavy computations (such as generating time slots and constructing events) to maintain UI responsiveness. The architecture follows a modular Vue component structure, with the main container managing state and child components handling specific UI elements (days, cells, events). It uses Vue's provide/inject pattern to pass down configuration and event data, and employs scoped slots for deep customization of event cards. The core library is framework-specific to Vue 2 but isolates concerns like date utilities and worker communication into reusable utilities. Despite its solid foundation, the repository shows signs of technical drift due to its reliance on Vue 2 and outdated build tools (Vue CLI 4, Rollup 1.x, Sass-loader 8.x). The last commit date appears to be in the future (2026-01-21), suggesting a lack of recent maintenance activity, and the project does not include automated tests. However, the utility functions and worker promise wrappers demonstrate reusable, non-obvious patterns that could be extracted for use in other projects.
Preview.js is a developer tool for live component previews integrated into IDEs (VS Code, IntelliJ) and available as a CLI. It analyzes source code to detect UI components and Storybook stories, extracts their props via a custom TypeScript type analyzer, and renders them in an isolated iframe powered by Vite with Hot Module Replacement. The system consists of a core server library (`@previewjs/core`), framework-specific plugins (React, Preact, Solid, Svelte, Vue 2/3), a virtual file system abstraction, and a type analysis engine. It targets frontend developers who want instant visual feedback on component changes without leaving their editor. The project is explicitly **no longer maintained** per the README, and the codebase shows signs of technical drift with outdated test apps and potential dependency stagnation. Despite its abandonment, the architecture is well-structured: a monorepo with clear separation of concerns (loader/worker pattern for isolate Vite servers, iframe controller, screenshot generator, serializable value handling). The type analyzer and virtual filesystem are reusable components that demonstrate non-obvious skill with TypeScript compiler API and abstract file access patterns.
This repository is a Vue.js single-page application that demonstrates the use of the Composition API via the @vue/composition-api plugin in a Vue 2 project. It fetches data from the CNode API to display a list of topics, includes a search bar for filtering, and uses WeUI for styling. The application consists of a few components (Header, Search, Panel) and a simple global store for state management. While the code is functional and correctly implements the Composition API patterns, it suffers from tight coupling to the global store, outdated dependencies, and a lack of error handling or loading states, making it suitable for learning but not for production use without significant improvements.
This repository implements a headless CMS architecture using Nuxt.js (v2.15) as the frontend and a full WordPress installation (v4.9.8) as the backend content source. The Nuxt application consumes WordPress REST API endpoints (extended by plugins like ACF to REST API, WP API Menus, and Contact Form 7) to render pages statically or server-side. The frontend includes custom Vue components for navigation, lazy-loaded images, a carousel slider, contact forms, and a deferred rendering mixin for performance. The WordPress backend is fully vendored within the repository, including core files, a custom theme that redirects WordPress routes to the Vue app, and numerous plugins for custom fields, user roles, SVG uploads, and CORS support. The project appears to be a starter template or production site for a headless WordPress + Nuxt stack, but the vendored WordPress core and outdated dependencies (WordPress 4.9.8, Nuxt 2.15, deprecated node-sass) indicate significant technical drift and maintenance challenges.
This repository is a Vue Router plugin that provides a fluent, Laravel-inspired API for defining routes. It allows developers to declare routes, redirects, nested groups, and route guards using a chainable syntax. The library is archived and retired in favor of a successor project called Routier. The core functionality includes a factory for managing route state, a route class for defining individual routes, and a guard base class for creating route middleware. Despite being archived, the code demonstrates solid engineering practices, particularly in the reusable Guard base class which implements a promise-based interception pattern.
Vue Native Core is a deprecated fork of Vue.js 2.x that compiles Vue component templates into render functions compatible with React Native (iOS/Android) and React Web. It provides a full reactive state management system (Vue's observer pattern), virtual DOM diffing, and a template compiler pipeline that transforms .vue single-file components into JavaScript modules usable by React Native's Metro bundler. The architecture mirrors Vue 2: core reactivity (Dep, Watcher, Scheduler), virtual DOM (createElement, patch), and a multi-stage compiler (parser → AST → code generator) with platform-specific backends for native and web. It also offers runtime helpers to emulate Vue directives (v-if, v-for, events) and component lifecycle in React. However, the project is explicitly deprecated, depends on outdated versions (Babel 6, React 16.8, React Native 0.45–0.59+), and uses deprecated React lifecycle methods (UNSAFE_componentWillMount). The codebase shows heavy modification of core Vue files, making it difficult to merge upstream updates, and its build system is complex and fragile. Despite these issues, the reactive state wrapper (Vue.observer) and the template-to-render compilers demonstrate non-trivial adaptation of Vue to React ecosystem.
This repository is a curated collection of front-end interview questions organized by topic (HTML, CSS, JavaScript, React, etc.). Each question links to a YouTube video with an answer. It is a static documentation resource, not a software application. There is no executable code, build system, or API. The content is well-structured but offers no reusable software components. The repository serves as a study guide for front-end developers preparing for technical interviews.
The repository "vue-tutorial" appears to be a tutorial for the Vue.js framework, as indicated by the README.md file which contains a table of contents linking to various Vue topics. However, the provided file tree only includes the README.md and Git metadata, with the actual tutorial content referenced in the `gh-pages` branch (not included in this analysis). Consequently, the core educational content cannot be evaluated from the given files. From the available information, the repository shows signs of recent activity (last commit dated 2026-03-30) and has 24 open issues, suggesting ongoing maintenance. No code-based dependencies or application logic are present in the analyzed file tree, eliminating concerns about technical drift or outdated dependencies. The repository does not contain any runnable application, library, or data processing code, limiting its reusability as a software component. As a result, no reusable components were identified in the source code, as the sole source file (README.md) serves as documentation rather than extractable code. The quality score reflects the absence of code-level craftsmanship, architecture, or reusable patterns, though the repository may still serve as a useful learning resource when the full tutorial content is considered.