mirror of
https://github.com/jhd3197/ServerKit.git
synced 2026-10-30 00:27:11 +09:00
Juan DenisandClaude Opus 5
ad32930d4f
js-yaml was pinned to 4.3.0 in the overrides block, so `npm audit fix` could never reach it -- the advisory (GHSA-5p4m-2wfm-xmqj, quadratic CPU in !!omap) sat permanently HIGH and masked anything landing behind it. Bumping the pin to 4.3.1 keeps the deliberate supply-chain pin and clears it. The other five were stale-lockfile problems: every fixed version already satisfied its parent's declared range, so re-resolution was enough and no dependency range changed. js-yaml 4.3.0 -> 4.3.1 GHSA-5p4m-2wfm-xmqj socket.io-parser 4.2.6 -> 4.2.7 GHSA-2m8v-j782-fhvr react-router 7.18.1 -> 7.18.2 GHSA-qwww-vcr4-c8h2 nanoid 3.3.16 -> 3.3.18 GHSA-2v37-7h3g-55p8 brace-expansion 1.1.16 -> 1.1.18 GHSA-mh99-v99m-4gvg, GHSA-rgw5-rvv9-x895 Only one of the six is reachable in a shipped panel at all: socket.io-parser runs in the browser, though an attacker must already control or MITM the panel's own websocket and the payoff is a hung operator tab. The react-router CSRF bypass is RSC-mode only and this is a declarative BrowserRouter SPA with no data router; js-yaml and brace-expansion are eslint-only; nanoid is build-time via postcss. Hygiene, not incident response. package.json and package-lock.json move together -- `npm ci` runs in frontend-ci.yml and release-smoke.yml and hard-fails if they disagree. Verified: npm audit reports 0 vulnerabilities, npm run lint passes with 0 errors, npm run build succeeds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
React Dashboard Template
A modern React dashboard application boilerplate built with Vite, featuring routing, charts, and a sidebar layout for building data-driven web interfaces.
Features
- React 18 with functional components and hooks
- Vite for fast development and building
- React Router for client-side routing
- Recharts for data visualization
- Lucide React for icons
- ESLint for code linting
- Responsive sidebar layout
- Dashboard page with sample components
Getting Started
Prerequisites
- Node.js 16+ and npm
Installation
- Clone or download this template
- Install dependencies:
npm install
Development
Start the development server:
npm run dev
The app will be available at http://localhost:41921.
Building for Production
Build the app for deployment:
npm run build
The output will be in the dist/ directory.
Preview Production Build
npm run preview
Project Structure
src/
├── App.jsx # Main app with routing
├── main.jsx # Entry point
├── index.css # Global styles
├── components/
│ └── Sidebar.jsx # Navigation sidebar
├── layouts/
│ └── DashboardLayout.jsx # Main layout wrapper
└── pages/
└── Dashboard.jsx # Main dashboard page
Customization
- Modify components in
src/components/ - Add new pages in
src/pages/ - Update routes in
App.jsx - Customize styles in
index.cssor component files
Environment Variables
Create a .env file in the root for environment variables:
VITE_API_URL=https://api.example.com
Access them in code via import.meta.env.VITE_API_URL.
Contributing
See the documentation files for AI agent permissions and guidelines.