typechecker

v9.3.0

Utilities to get and check variable types (isString, isPlainObject, isRegExp, etc) For more information about how to use this package see README

Latest version published 4 months ago

License: Artistic-2.0

NPM

GitHub

Package Health Score

72 / 100

security
No known security issues
popularity
Popular
maintenance
Sustainable
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
9.3.0	\|	12/2023		0 C 0 H 0 M 0 L	0 H 1 M 0 L
9.2.0	\|	12/2023		0 C 0 H 0 M 0 L	0 H 1 M 0 L
8.6.0	\|	11/2023		0 C 0 H 0 M 0 L	0 H 1 M 0 L
7.18.0	\|	07/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.11.0	\|	11/2019	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Artistic-2.0

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (209,164)

GitHub Stars: 47
Forks: 9
Contributors: 7

Direct Usage Popularity

The npm package typechecker receives a total of 209,164 downloads a week. As such, we scored typechecker popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package typechecker, we found that it has been starred 47 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: No
Contributors: 7
Funding: Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like typechecker is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 4
Open PR: 0
Last Release: 4 months ago
Last Commit: 4 months ago

Further analysis of the maintenance status of typechecker based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that typechecker demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=4

Age: 11 years
Dependencies: 1 Direct
Versions: 136
Install Size: 106 kB
Dist-tags: 2
# of Files: 18
Maintainers: 1
TS Typings: Yes

typechecker has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use typechecker?

To help you get started, we've collected the most common ways that typechecker is being used within popular public projects.

bevry / boundation / source / package.js View on Github

const result = arrangekeys(
				edition,
				'description directory entry tags engines'
			)
			if (result.tags) result.tags = Array.from(result.tags.values())
			return result
		})
	} else {
		delete packageData.editions
	}

	// trim empty keys
	for (const key in packageData) {
		if (packageData.hasOwnProperty(key)) {
			const value = packageData[key]
			if (typeChecker.isArray(value) && typeChecker.isEmptyArray(value)) {
				console.log(`trim: array: package.json:${key}`)
				delete packageData[key]
			} else if (
				typeChecker.isPlainObject(value) &&
				typeChecker.isEmptyPlainObject(value)
			) {
				console.log(`trim: empty: package.json:${key}`)
				delete packageData[key]
			} else if (value == null || value === '') {
				console.log(`trim: null|'': package.json:${key}`)
				delete packageData[key]
			}
		}
	}

	// ---------------------------------

View more ways to use typechecker

TypeChecker

Utilities to get and check variable types (isString, isPlainObject, isRegExp, etc)

Why?

Why should I use this instead of say instanceof?

Under certain circumstances instanceof may not return the correct results. This occurs with node's vm module especially, and circumstances where an object's prototype has been dereferenced from the original. As such, for basic == and === checks (like a === null), you're fine not using this, but for checks when you would have done instanceof (like err instanceof Error), you should try to use this instead. Plus things like isPlainObject are darn useful!

Usage

Complete API Documentation.

Install

npm

Install: npm install --save typechecker
Import: import * as pkg from ('typechecker')
Require: const pkg = require('typechecker')

Deno

import * as pkg from 'https://unpkg.com/typechecker@^9.4.0/edition-deno/index.ts'

Skypack

unpkg

jspm

Editions

This package is published with the following editions:

typechecker aliases typechecker/index.cjs which uses the Editions Autoloader to automatically select the correct edition for the consumer's environment
typechecker/source/index.ts is TypeScript source code with Import for modules
typechecker/edition-browsers/index.js is TypeScript compiled against ES2022 for web browsers with Import for modules
typechecker/edition-es2022/index.js is TypeScript compiled against ES2022 for Node.js 6 || 8 || 10 || 12 || 14 || 16 || 18 || 20 || 21 with Require for modules
typechecker/edition-es5/index.js is TypeScript compiled against ES5 for Node.js 4 || 6 || 8 || 10 || 12 || 14 || 16 || 18 || 20 || 21 with Require for modules
typechecker/edition-es2022-esm/index.js is TypeScript compiled against ES2022 for Node.js 12 || 14 || 16 || 18 || 20 || 21 with Import for modules
typechecker/edition-types/index.d.ts is TypeScript compiled Types with Import for modules
typechecker/edition-deno/index.ts is TypeScript source code made to be compatible with Deno

History

Discover the release history by heading on over to the HISTORY.md file.

Backers

Code

Discover how to contribute via the CONTRIBUTING.md file.

Authors

Benjamin Lupton — Accelerating collaborative wisdom.

Maintainers

Benjamin Lupton — Accelerating collaborative wisdom.

Contributors

Finances

Donors

License

Unless stated otherwise all works are:

and licensed under:

Artistic License 2.0

typechecker dependencies

editions

typechecker development dependencies

@types/node @typescript-eslint/eslint-plugin @typescript-eslint/parser assert-helpers eslint eslint-config-bevry eslint-config-prettier eslint-plugin-prettier kava make-deno-edition prettier projectz typedoc typescript valid-directory valid-module

FAQs

What is typechecker?

Utilities to get and check variable types (isString, isPlainObject, isRegExp, etc). Visit Snyk Advisor to see a full health score report for typechecker, including popularity, security, maintenance & community analysis.

Is typechecker popular?

The npm package typechecker receives a total of 209,164 weekly downloads. As such, typechecker popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is typechecker well maintained?

We found indications that typechecker maintenance is sustainable demonstrating some project activity. We saw a total of 7 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is typechecker safe to use?

The npm package typechecker was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 15 April-2024, at 03:17 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (209,164)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use typechecker?

TypeChecker

Why?

Usage

Install

npm

Deno

Skypack

unpkg

jspm

Editions

History

Backers

Code

Authors

Maintainers

Contributors

Finances

Sponsors

Donors

License

typechecker dependencies

typechecker development dependencies

FAQs

What is typechecker?

Is typechecker popular?

Is typechecker well maintained?

Is typechecker safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues