1. Advisor
  2. JavaScript packages
  3. wct-browser-legacy

wct-browser-legacy

v1.0.2

Client-side dependencies for web-component-tester tests installed via npm. For more information about how to use this package see README

Latest version published 6 years ago
License: BSD-3-Clause
NPM
GitHub

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

51 / 100

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
1.0.2 | 10/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 05/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
Security Policy
No

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

Small

Weekly Downloads (2,429)

Download trend
GitHub Stars
567
Forks
176
Contributors
-

Direct Usage Popularity

Occasionally

The npm package wct-browser-legacy receives a total of 2,429 downloads a week. As such, we scored wct-browser-legacy popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package wct-browser-legacy, we found that it has been starred 567 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
No
Contributing.md
No
Code of Conduct
No
Contributors
0
Funding
No

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that wct-browser-legacy is missing a README file.

Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
25
Last Release
6 years ago
Last Commit
6 years ago

Further analysis of the maintenance status of wct-browser-legacy 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 wct-browser-legacy 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

scan-reversed

Check your package.json

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

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
7 years
Dependencies
12 Direct
Versions
15
Install Size
200 kB
Dist-tags
1
# of Files
11
Maintainers
10
TS Typings
No

wct-browser-legacy 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.