npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

ui-code-insight

v2.1.2

Published

Interactive CLI for generating code quality, style, and package analysis reports for JavaScript, TypeScript, CSS, and modern web projects.

Downloads

51

Readme

UI Insights Report Generator (ui-code-insight)

Your all-in-one CLI for auditing, visualizing, and improving code quality, security, and maintainability in modern JavaScript, TypeScript, and CSS projects. Instantly generate actionable dashboards and reports—no setup required.


🚀 Quick Start

npx ui-code-insight

No install, no config, instant insights.

📊 Live Demo

Check out the Audit Sample Dashboard to see the tool in action with sample projects!


🌟 Why Use UI Code Insight?

| Feature | Benefit | |------------------------|-----------------------------------------| | Interactive CLI | No config needed, just run and go | | Multi-framework support| Works with React, Node, TS, Vanilla JS | | Comprehensive audits | Security, Performance, Accessibility... | | Smart dependency mgmt | Installs only what you need | | Visual dashboard | See all issues in one place | | Live demo available | Try it now |


📦 Usage Examples

🎯 Live Demo

Experience the full UI Code Insight dashboard with sample projects: Audit Sample Dashboard

CLI Prompt Example

? What type of project is this? (Use arrow keys)
❯ React

? Would you like to install all required dependencies for React? (Y/n)
❯ Yes

Installing missing dependencies: eslint-plugin-jsx-a11y eslint-config-airbnb
✅ Dependencies installed successfully!

? Which report(s) do you want to generate? (Press <space> to select, <a> to toggle all, <i> to invert selection)
❯◯ ESLint
 ◯ Stylelint
 ◯ Package Report
 ◯ Security Audit
 ◯ Performance Audit
 ◯ Accessibility Audit
 ◯ Modern Practices Audit
 ◯ Testing Audit
 ◯ Dependency Audit
 ◯ Comprehensive Audit (All Categories)
 ◯ All Traditional Reports

Sample Report Output (JSON)

{
  "category": "security",
  "issues": [
    {
      "file": "src/server.js",
      "line": 42,
      "severity": "high",
      "message": "Hardcoded secret detected",
      "snippet": "const password = 'supersecret';"
    }
  ]
}

🛠️ Supported Project Types

  • React
  • Node.js
  • Vanilla JavaScript
  • TypeScript
  • TypeScript + React

🔍 Audit Categories At a Glance

  • 🔒 Security: Find secrets, XSS, vulnerable deps
  • Performance: Flag large bundles, dead code
  • Accessibility: Check alt text, headings, ARIA
  • 🧪 Testing: Detect missing or weak tests
  • 📦 Dependencies: Outdated, unused, or risky packages

🛡️ How It Works

  1. Select audits via CLI: Choose which audits to run.
  2. File scanning: Scans your codebase, excluding common build/output folders.
  3. Pattern matching & analysis: Uses static analysis and best-practice checks.
  4. Report generation: Saves results as JSON in the report/ directory.
  5. Dashboard visualization: View all results in a single dashboard.

⚙️ Configuration

Do I need a config file?

  • No! Defaults work for most users. Just run and go.
  • For custom file patterns or advanced settings, create ui-code-insight.config.json in your project root.

ui-code-insight.config.json Reference

You can customize how files are scanned and which rules are excluded by adding a ui-code-insight.config.json file to your project root. Example:

{
  "jsFilePathPattern": [
    "./src/**/*.js",
    "./src/**/*.ts",
    "./src/**/*.jsx",
    "./src/**/*.tsx",
    "!./dist/**",
    "!./build/**"
  ],
  "htmlFilePathPattern": [
    "**/*.{html,js,ts,jsx,tsx}",
    "!**/node_modules/**"
  ],
  "scssFilePathPattern": [
    "**/*.{scss,css,less}",
    "!**/node_modules/**"
  ],
  "excludeRules": {
    "eslint": {
      "enabled": true,
      "overrideDefault": false,
      "additionalRules": ["my-custom-rule"]
    },
    "stylelint": {
      "enabled": true,
      "overrideDefault": false,
      "additionalRules": ["my-custom-style-rule"]
    },
    "dependency": {
      "enabled": true,
      "overrideDefault": false,
      "additionalRules": ["custom-dependency-rule"]
    }
    // ... other audit types ...
  }
}
  • jsFilePathPattern, htmlFilePathPattern, scssFilePathPattern: Glob patterns for files to include/exclude in audits.
  • excludeRules: Fine-tune which rules are enabled/disabled for each audit type. You can add custom rules or override defaults.

⚠️ Important Usage Note

Do not run 'Comprehensive Audit (All Categories)' and 'All Traditional Reports' together on large projects.

Running both at the same time may cause the tool to crash or run out of memory on large codebases. For best results, run one or the other, not both together.


❓ FAQ

Q: How accurate are the reports?
A:

  • Rule-Based Static Analysis: The tool uses established static analysis engines (like ESLint, Stylelint, and custom audits) that apply well-known rules and patterns to your codebase. The accuracy of each report is tied to the quality and completeness of these rules.
  • Coverage of Patterns: The tool looks for a wide range of issues, but it can only find what it’s programmed to detect. If an issue falls outside these patterns, it won’t be flagged.
  • No False Positives/Negatives Guarantee: Like all static analysis tools, there may be false positives (flagging something that isn’t really a problem) or false negatives (missing a real issue). The tool aims to minimize these by using up-to-date, community-accepted rules and by allowing configuration for project-specific needs.
  • Transparency and Customization: The tool outputs detailed reports, so users can review and verify each finding. Users can customize rules or add exceptions to improve relevance and reduce noise.
  • Not a Substitute for Manual Review: Automated tools are a first line of defense and help catch common issues quickly. For critical applications, manual code review and testing are still recommended to catch context-specific or business-logic issues.

Q: Do I need to configure anything?
A: No! Defaults work for most users. Advanced users can add a config file.

Q: Where are reports saved?
A: In the report/ directory at your project root.


Dependencies


Repository

GitHub: https://github.com/deepak121001/ui-code-insight.git

📊 Live Demo & Samples

  • Audit Sample Dashboard: https://deepak121001.github.io/Audit-Sample/
  • Sample Projects: Explore React, Node.js, and Vanilla JavaScript projects with intentional issues for testing
  • Interactive Reports: View ESLint, Stylelint, Security, Accessibility, and Performance audits in action

🤝 Contributing

Contributions, issues, and feature requests are welcome! Feel free to check issues or open a pull request.

  1. Fork the repo
  2. Create your feature branch (git checkout -b feature/YourFeature)
  3. Commit your changes (git commit -am 'Add new feature')
  4. Push to the branch (git push origin feature/YourFeature)
  5. Open a pull request

🗺️ Roadmap

  • [ ] AI-powered code suggestions
  • [ ] More framework support
  • [ ] Customizable dashboard themes

📝 License

This project is licensed under the MIT License.

Dashboard Overview