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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@razmans/ts-score-check

v1.0.7

Published

TypeScript score check

Readme

TypeScript Score Check

A CLI tool to score TypeScript code for best practices and simplicity.

Features

  • Scores TypeScript files for adherence to best practices.
  • Metrics evaluated:
    • Avoid use of any
    • Explicit return types for functions
    • Use of access modifiers
    • Code complexity
    • Nesting depth
    • Prefer const over let
    • Avoid type assertions
    • Use of readonly for properties
    • Avoid use of var
    • Use of optional chaining
  • Human-readable and JSON output
  • Suggestions for improving code quality

Usage

Command Line Interface


# Analyze a single file
npx @razmans/ts-score-check ./src/test.ts

# Analyze an entire directory
npx @razmans/ts-score-check ./src

Output

For each file, you get:

  • File path
  • Score (0-100)
  • Metrics breakdown (percentage for each metric)
  • Suggestions for improvement

How Scoring Works

  • Each metric is weighted (see functions/helper.ts).
  • The score is a weighted sum of all metrics, normalized to 100.
  • Suggestions are generated for metrics that are not perfect.

Project Structure

  • index.ts — CLI entry point
  • functions/ — Scoring logic and helpers
  • test/ — Example TypeScript files for testing

Requirements

License

MIT