@tanker/errors

v4.2.0

Tanker SDK (common error classes) For more information about how to use this package see README

Latest version published 6 months ago
License: Apache-2.0

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

61 / 100

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
4.2.0 | 06/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.1.1 | 01/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.3.2 | 05/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.32.2 | 08/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.31.0 | 05/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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

Small

Weekly Downloads (1,805)

Download trend
GitHub Stars
798
Forks
25
Contributors
20

Direct Usage Popularity


The npm package @tanker/errors receives a total of 1,805 downloads a week. As such, we scored @tanker/errors popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @tanker/errors, we found that it has been starred 798 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
No
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the @tanker/errors 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 @tanker/errors is missing a Code of Conduct.

How about a good first contribution to this project? It seems that @tanker/errors is missing a README file.


Embed Package Health Score Badge

package health: 61/100 package health 61/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
6 months ago
Last Commit
16 days ago

Further analysis of the maintenance status of @tanker/errors based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that @tanker/errors 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.

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
1 Direct
Versions
276
Install Size
88.5 kB
Dist-tags
3
# of Files
147
Maintainers
4
TS Typings
No

@tanker/errors 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.