gcc-explorer

v0.0.3

Interactively investigate compiler output For more information about how to use this package see README

Latest version published 8 years ago
License: BSD-2-Clause

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

63 / 100

Security

Security review needed
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.3 | 09/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-2-Clause
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

Small

Weekly Downloads (1)

Download trend
GitHub Stars
16.15K
Forks
1.72K
Contributors
410

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package gcc-explorer, we found that it has been starred 16,152 times.

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

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
410
Funding
Yes

A good and healthy external contribution signal for gcc-explorer project, which invites more than one hundred open source maintainers to collaborate on the repository.


Embed Package Health Score Badge

package health: 63/100 package health 63/100

Maintenance

Inactive

Commit Frequency

Open Issues
752
Open PR
27
Last Release
8 years ago
Last Commit
8 days ago

Further analysis of the maintenance status of gcc-explorer 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 gcc-explorer 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.

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
0.1

Age
8 years
Dependencies
13 Direct
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

gcc-explorer 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.