merge-source-map

v1.1.0

Merge old source map and new source map in multi-transform flow

MIT
Latest version published 4 years ago
    npm install merge-source-map
  

Package Health Score

65 / 100

Security

No known security issues
Powered by Snyk
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.1.0 | 12/2017
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.4 | 06/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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test merge-source-map
Get started free

Popularity

Influential project

Weekly Downloads (3,920,479)

Download trend
Dependents
115
GitHub Stars
23
Forks
4
Contributors
3

Direct Usage Popularity

TOP 10%

The npm package merge-source-map receives a total of 3,920,479 downloads a week. As such, we scored merge-source-map popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package merge-source-map, we found that it has been starred 23 times, and that 115 other projects in the ecosystem are dependent on it.

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
Yes
Contributing.md
No
Code of Conduct
No
Contributors
3
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like merge-source-map is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 65/100 package health 65/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
2
Open PR
1
Last Release
4 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of merge-source-map 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 merge-source-map 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.

Package

Node.js Compatibility
not defined

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

merge-source-map 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.