pwned

v12.1.1

A command-line tool for querying the 'Have I been pwned?' service. For more information about how to use this package see README

Latest version published 4 months ago
License: MIT

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

72 / 100

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
12.1.1 | 07/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
12.0.0 | 11/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.0.0 | 05/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.0.1 | 11/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.0.0 | 09/2020
  • 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.

Get started free

Popularity

Limited

Weekly Downloads (33)

Download trend
GitHub Stars
228
Forks
27
Contributors
5

Direct Usage Popularity


The npm package pwned receives a total of 33 downloads a week. As such, we scored pwned popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package pwned, we found that it has been starred 228 times.

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

Community

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
5
Funding
Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like pwned is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 72/100 package health 72/100

Maintenance

Sustainable

Commit Frequency

Open Issues
2
Open PR
0
Last Release
4 months ago
Last Commit
25 days ago

Further analysis of the maintenance status of pwned based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that pwned demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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
>=18.0.0

Age
9 years
Dependencies
9 Direct
Versions
45
Install Size
81.5 kB
Dist-tags
3
# of Files
34
Maintainers
1
TS Typings
No

pwned 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.