30-days-of-javascript

v3.3.5

30-days-of-javascript For more information about how to use this package see README

Latest version published 7 months ago
License: MIT

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

30-days-of-javascript is a malicious package. The attack chain is triggered by package installation via an install hook in the package.json. The malicious code constructs an object o that aggregates various pieces of system information, such as the operating system's platform, architecture, release version, CPU information, network interfaces, and user information after which it exfiltrates the data to a malicious host. 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
2.3.4 | 04/2024
  • 0
    H
  • 0
    M
  • 0
    L
3.3.5 | 04/2024
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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 (5)

Download trend
GitHub Stars
43.21K
Forks
10.02K
Contributors
50

Direct Usage Popularity


The npm package 30-days-of-javascript receives a total of 5 downloads a week. As such, we scored 30-days-of-javascript popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package 30-days-of-javascript, we found that it has been starred 43,214 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
50
Funding
No

With more than 10 contributors for the 30-days-of-javascript 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 30-days-of-javascript is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 43/100 package health 43/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
102
Open PR
243
Last Release
7 months ago
Last Commit
1 year ago

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

We found that 30-days-of-javascript demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
not defined

Age
7 months
Dependencies
4 Direct
Versions
5
Install Size
67.8 kB
Dist-tags
1
# of Files
37
Maintainers
1
TS Typings
No

30-days-of-javascript 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.