Package Health Score

53 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Sustainable

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

Version				Vulnerabilities	License Risk
2.0.0	\|	01/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

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

Recognized

Weekly Downloads (10,850)

GitHub Stars: 297
Forks: 58
Contributors: 20

Direct Usage Popularity

The npm package assert-browserify receives a total of 10,850 downloads a week. As such, we scored assert-browserify popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package assert-browserify, we found that it has been starred 297 times.

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

Community

Sustainable

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

With more than 10 contributors for the assert-browserify repository, this is possibly a sign for a growing and inviting community.

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

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 3
Open PR: 3
Last Release: 4 years ago
Last Commit: 1 year ago

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

An important project maintenance signal to consider for assert-browserify is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

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: not defined

Age: 4 years
Dependencies: 4 Direct
Versions: 2
Install Size: 75.3 kB
Dist-tags: 1
# of Files: 8
Maintainers: 1
TS Typings: Yes

assert-browserify 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.

Readme

assert

The assert module from Node.js, for the browser.

With browserify, simply require('assert') or use the assert global and you will get this module.

The goal is to provide an API that is as functionally identical to the Node.js assert API as possible. Read the official docs for API documentation.

Install

To use this module directly (without browserify), install it as a dependency:

npm install assert

Usage

The goal is to provide an API that is as functionally identical to the Node.js assert API as possible. Read the official docs for API documentation.

Inconsistencies with Node.js `assert`

Due to differences between browsers, some error properties such as message and stack will be inconsistent. However the assertion behaviour is as close as possible to Node.js and the same error code will always be used.

Contributing

To contribute, work on the source files. Then build and run the tests against the built files. Be careful to not introduce syntax that will be transpiled down to unsupported syntax. For example, for...of loops will be transpiled to use Symbol.iterator which is unavailable in IE.

Build scripts

`npm run build`

Builds the project into the build dir.

`npm run dev`

Watches source files for changes and rebuilds them into the build dir.

`npm run test`

Builds the source files into the build dir and then runs the tests against the built project.

`npm run test:nobuild`

Runs the tests against the built project without rebuilding first.

This is useful if you're debugging in the transpiled code and want to re-run the tests without overwriting any changes you may have made.

`npm run test:source`

Runs the tests against the unbuilt source files.

This will only work on modern Node.js versions.

`npm run test:browsers`

Run browser tests against the all targets in the cloud.

Requires airtap credentials to be configured on your machine.

`npm run test:browsers:local`

Run a local browser test server. No airtap configuration required.

When paired with npm run dev any changes you make to the source files will be automatically transpiled and served on the next request to the test server.

License

assert-browserify dependencies

es6-object-assign is-nan object-is util

assert-browserify development dependencies

@babel/cli @babel/core @babel/preset-env airtap array-fill core-js cross-env object.entries object.getownpropertydescriptors tape

FAQs

What is assert-browserify?

The assert module from Node.js, for the browser. Visit Snyk Advisor to see a full health score report for assert-browserify, including popularity, security, maintenance & community analysis.

Is assert-browserify popular?

The npm package assert-browserify receives a total of 10,850 weekly downloads. As such, assert-browserify popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is assert-browserify well maintained?

We found indications that assert-browserify is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is assert-browserify safe to use?

The npm package assert-browserify 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 4 November-2024, at 04:15 (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 (10,850)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

assert

Install

Usage

Inconsistencies with Node.js assert

Contributing

Build scripts

npm run build

npm run dev

npm run test

npm run test:nobuild

npm run test:source

npm run test:browsers

npm run test:browsers:local

License

assert-browserify dependencies

assert-browserify development dependencies

FAQs

What is assert-browserify?

Is assert-browserify popular?

Is assert-browserify well maintained?

Is assert-browserify 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

Inconsistencies with Node.js `assert`

`npm run build`

`npm run dev`

`npm run test`

`npm run test:nobuild`

`npm run test:source`

`npm run test:browsers`

`npm run test:browsers:local`