package-name-fixer

v1.0.9

Goes into package.json and update the name to match the Github repository. Also updates author, description. It's useful when a npm repo is build out of a template. For more information about how to use this package see README

Latest version published 9 months ago

License: MIT

NPM

GitHub

Package Health Score

53 / 100

security
No known security issues
popularity
Limited
maintenance
Inactive
community
Limited

Explore Similar Packages

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
1.0.9	\|	01/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

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

Limited

Weekly Downloads (2)

GitHub Stars: 0
Forks: 0
Contributors: 1

Direct Usage Popularity

The npm package package-name-fixer receives a total of 2 downloads a week. As such, we scored package-name-fixer popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package package-name-fixer, we found that it has been starred ? times.

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: 1
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like package-name-fixer is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 9 months ago
Last Commit: 9 months ago

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

We found that package-name-fixer 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.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=14.0.0

Age: 9 months
Dependencies: 0 Direct
Versions: 11
Install Size: 149 kB
Dist-tags: 1
# of Files: 9
Maintainers: 1
TS Typings: No

package-name-fixer 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.

Readme

package-name-fixer

Goes into package.json and update the name to match the Github repository. Also updates author, description. It's useful when a npm repo is build out of a template.

Written using bun

Usage

$ bun start

Usage from another package

Update package.json:

{
  //...
  "scripts": {
    //...
    "fix-package-name": "npm explore package-name-fixer -- bun start \"$(pwd)\""
  },
  "devDependencies": {
    //...
    "package-name-fixer": "^1.0.9",
  }
}

package-name-fixer development dependencies

@types/bun jest ts-jest

FAQs

What is package-name-fixer?

Goes into package.json and update the name to match the Github repository. Also updates author, description. It's usefu... Visit Snyk Advisor to see a full health score report for package-name-fixer, including popularity, security, maintenance & community analysis.

Is package-name-fixer popular?

The npm package package-name-fixer receives a total of 2 weekly downloads. As such, package-name-fixer popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is package-name-fixer well maintained?

We found indications that package-name-fixer is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is package-name-fixer safe to use?

The npm package package-name-fixer was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 6 November-2024, at 03:17 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (2)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

package-name-fixer

Usage

Usage from another package

package-name-fixer development dependencies

FAQs

What is package-name-fixer?

Is package-name-fixer popular?

Is package-name-fixer well maintained?

Is package-name-fixer safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues