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

@bhupesh123/type-error

v1.0.0

Published

Type error detection microservice for GitHub repositories using MCP

Readme

@github-analyzer/type-error

Type error detection microservice for GitHub repositories using GitHub MCP (Model Context Protocol).

Installation

npm install -g @github-analyzer/type-error

Usage

CLI

# Analyze a repository
type-error analyze --owner microsoft --repo vscode --branch main --token YOUR_GITHUB_TOKEN

# Disable MCP integration
type-error analyze --owner microsoft --repo vscode --no-mcp

# Or use environment variable
export GITHUB_TOKEN=your_token_here
type-error analyze --owner microsoft --repo vscode

Programmatic API

import { TypeErrorAnalyzer } from '@github-analyzer/type-error';

const analyzer = new TypeErrorAnalyzer('YOUR_GITHUB_TOKEN', true);

const result = await analyzer.analyzeRepository('microsoft', 'vscode', 'main');

console.log(`Total Type Errors: ${result.totalErrors}`);
console.log(`Language: ${result.languageInfo.language}`);
console.log(result.errors);

Features

  • Detects type errors in TypeScript, JavaScript, Python, Java, and Go
  • Integrates with GitHub MCP for advanced type checking
  • Analyzes GitHub Check Runs for type errors
  • Provides detailed error reports with file, line, and column information
  • Categorizes errors by type (implicit-any, type-annotation, etc.)
  • Auto-detects language and configuration files

GitHub MCP Integration

This tool leverages GitHub's Model Context Protocol (MCP) to access advanced type checking information from GitHub's code analysis infrastructure. MCP provides:

  • Real-time type checking results from GitHub Actions
  • Integration with language servers
  • Access to check run annotations
  • Enhanced error detection

API

TypeErrorAnalyzer

Constructor

new TypeErrorAnalyzer(githubToken: string, mcpEnabled?: boolean)

Methods

analyzeRepository(owner, repo, branch?)

Analyzes a GitHub repository for type errors.

Parameters:

  • owner (string): Repository owner
  • repo (string): Repository name
  • branch (string, optional): Branch name (default: 'main')

Returns: Promise<TypeAnalysisResult>

Supported Languages

  • TypeScript (.ts, .tsx)
  • JavaScript (.js, .jsx)
  • Python (.py)
  • Java (.java)
  • Go (.go)

License

MIT