Alert
Unable to verify the project's public source code repository.
  1. Advisor
  2. JavaScript packages
  3. cvs-components

cvs-components

v0.0.1-security

security holding package

Latest version published 2 years ago
License: Unknown
NPM

Ensure you're using the healthiest npm packages

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

This is a malicious package

cvs-components is a malicious package. This package contains a malware that includes a reverse shell code and binds shell scripts. As these packages are dependancy confusion packages, these packages are malicious if they have been downloaded and installed from the npm repository. Installation of these packages from other repositories or CDNs are likely safe to use. These spoofed packages have no relation to the company or project they are attempting to spoof, and are not published by them or associated with them in any way. Users should verify that the package they are using has been downloaded from the official source and not from the general package distribution repository. Snyk cannot automatically identify where a package has been downloaded from and will mark any use of the package as malicious to allow users to check whether they have been compromised. Avoid using all malicious instances of the package.

Security

Security issues found
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
0.0.1-security | 11/2022
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
Unknown
Alert

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.

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

Limited

Weekly Downloads (1)

Download trend
GitHub Stars
?
Forks
?
Contributors
-

Direct Usage Popularity

The npm package cvs-components receives a total of 1 downloads a week. As such, we scored cvs-components popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package cvs-components, we found that it has been starred ? 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.

Embed Package Health Score Badge

package health: 16/100 package health 16/100

Maintenance

Inactive

Commit Frequency

Unavailable commit data
Open Issues
?
Open PR
?
Last Release
2 years ago
Last Commit
unknown

Further analysis of the maintenance status of cvs-components 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 cvs-components 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
2 years
Dependencies
0 Direct
Versions
7
Install Size
434 B
Dist-tags
1
# of Files
2
Maintainers
1
TS Typings
No

cvs-components 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.