The npm package replace-in-file receives a total of 265,586 downloads a week. As such, we scored replace-in-file popularity level to be Popular.
Based on project statistics from the GitHub repository for the npm package replace-in-file, we found that it has been starred 350 times, and that 3,783 other projects on 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.
Snyk detected that the latest version of replace-in-file has a security vulnerability.
We highly advise you to review these security issues.
You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.
We found a way for you to contribute to the project! Looks like replace-in-file is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test replace-in-file
Further analysis of the maintenance status of replace-in-file based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.
We found that replace-in-file demonstrates a positive version release cadence with at least one new version released in the past 12 months.
In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.
With more than 10 contributors for the replace-in-file 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 replace-in-file is missing a Code of Conduct.
We detected a total of 40 direct & transitive dependencies for replace-in-file. See the full dependency tree of replace-in-file
replace-in-file 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.