globaloffensive

v3.2.0

Exposes a simple API for interacting with the Counter-Strike: Global Offensive/CS2 game coordinator For more information about how to use this package see README

Latest version published 1 month 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

Package Health Score

75 / 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
3.2.0 | 10/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.0 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.3.1 | 09/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.2 | 10/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.6 | 04/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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 (1,743)

Download trend
GitHub Stars
260
Forks
61
Contributors
9

Direct Usage Popularity

TOP 30%

The npm package globaloffensive receives a total of 1,743 downloads a week. As such, we scored globaloffensive popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package globaloffensive, we found that it has been starred 260 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
9
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 75/100 package health 75/100

Maintenance

Healthy

Commit Frequency

Open Issues
8
Open PR
4
Last Release
1 month ago
Last Commit
1 month ago

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

We found that globaloffensive demonstrates a positive version release cadence with at least one new version released in the past 3 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
>=14.0.0

Age
10 years
Dependencies
5 Direct
Versions
33
Install Size
16.5 MB
Dist-tags
1
# of Files
39
Maintainers
1
TS Typings
No

globaloffensive 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.