Homepage

fix-bad-declaration-output vulnerabilities

Do you have bad declarations? Is it too hard to fix complex tooling? (Or do you not have the time to learn how?)
Licenses: MIT
Published: 1 years ago Last updated: 2 months ago Latest version: 1.1.5 Latest non-vulnerable version: 1.1.5
npm
GitHub

Package Health Score

61/100
  • securitySecurity review needed
  • popularitySmall
  • maintenanceHealthy
  • communityLimited

Maintenance

HEALTHY

Commit Frequency

Loading chart...

Open Issues
2
Open PR
0
New PRS
0
Last Release
2 months ago
Last Commit
2 months ago
Maintainers
1

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

We found that fix-bad-declaration-output demonstrates a positive version release cadence with at least one new version released in the past 3 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.

Popularity

SMALL
Weekly downloads (2.4k)
GitHub Stars
2
Forks
1
Contributors
0

The npm package fix-bad-declaration-output receives a total of 2,362 downloads a week. As such, we scored fix-bad-declaration-output popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package fix-bad-declaration-output, we found that it has been starred 2 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
0
Funding
No
LICENSE
MIT

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like fix-bad-declaration-output is missing a Code of Conduct.

License

MIT>=0;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

SECURITY REVIEW NEEDED
Show only direct vulnerabilities in latest version

No vulnerabilities found in the latest version

No vulnerabilities found

Package versions

10 VERSIONS IN TOTAL
versionpublisheddirect vulnerabilities
1.1.522 Aug, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.420 Mar, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.319 Mar, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.29 Feb, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.13 Feb, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.01 Feb, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.323 Jan, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.223 Jan, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.110 Jan, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.0.09 Jan, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

fix-bad-declaration-output dependencies

4 IN TOTAL
@babel/parserfs-extraglobbyjscodeshift

fix-bad-declaration-output development dependencies

16 IN TOTAL
@arethetypeswrong/cli@nullvoxpopuli/eslint-configs@tsconfig/node21@tsconfig/strictest@types/common-tags@types/fs-extra@types/jscodeshift@types/nodecommon-tagsconcurrentlyeslintprettierpublintrelease-plantypescriptvitest