@iota/transaction

v1.0.0-beta.30

IOTA transaction (de)serialization & guards.

Apache-2.0
Latest version published 1 year ago
    npm install @iota/transaction
  

Package Health Score

67 / 100

Popularity

Small

Weekly Downloads (4,047)

Download trend
Dependents
0
GitHub Stars
954
Forks
294
Contributors
50

Direct Usage Popularity

TOP 30%

The npm package @iota/transaction receives a total of 4,047 downloads a week. As such, we scored @iota/transaction popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @iota/transaction, we found that it has been starred 954 times, and that 0 other projects in 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

06/2020

Direct Vulnerabilities

Popular
1.0.0-beta.30
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
1.0.0-beta.30
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.0.0-beta.30
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
Apache-2.0

Security Policy
Yes

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test @iota/transaction
Keep your project free of vulnerabilities with Snyk

Maintenance

Sustainable

Commit Frequency

Open Issues
1
Open PR
1
Last Release
1 year ago
Last Commit
6 days ago

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

An important project maintenance signal to consider for @iota/transaction is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

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.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
50
Funding
No

With more than 10 contributors for the @iota/transaction repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Package

Node.js Compatibility
not defined

Age
3 years
Dependencies
6 Direct
Versions
40
Install Size
347 kB
Dist-tags
2
# of Files
35
Maintainers
9
TS Typings
Yes

@iota/transaction 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.