@liskhq/lisk-transactions

v6.1.0

Utility functions related to transactions according to the Lisk protocol For more information about how to use this package see README

Latest version published 11 months ago

License: Apache-2.0

NPM

GitHub

Package Health Score

61 / 100

security
No known security issues
popularity
Popular
maintenance
Inactive
community
Active

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
6.1.0	\|	12/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.0.0	\|	11/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.3.0	\|	09/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.0	\|	11/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.0.2	\|	02/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

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

Popular

Weekly Downloads (14,415)

GitHub Stars: 2.72K
Forks: 454
Contributors: 70

Direct Usage Popularity

The npm package @liskhq/lisk-transactions receives a total of 14,415 downloads a week. As such, we scored @liskhq/lisk-transactions popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @liskhq/lisk-transactions, we found that it has been starred 2,722 times.

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

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 70
Funding: No

With more than 10 contributors for the @liskhq/lisk-transactions repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Inactive

archived

Commit Frequency

Open Issues: 53
Open PR: 1
Last Release: 11 months ago
Last Commit: 10 months ago

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

We found that @liskhq/lisk-transactions 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: >=18.12.0 <=18

Age: 6 years
Dependencies: 3 Direct
Versions: 46
Install Size: 41.2 kB
Dist-tags: 1
# of Files: 25
Maintainers: 3
TS Typings: No

@liskhq/lisk-transactions 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.

Not sure how to use @liskhq/lisk-transactions?

To help you get started, we've collected the most common ways that @liskhq/lisk-transactions is being used within popular public projects.

LiskHQ / lisk-sdk-examples / transport / client / scripts / print_sendable_register_packet.js View on Github

const RegisterPacketTransaction = require('../transactions/register-packet');
const transactions = require('@liskhq/lisk-transactions');
const { EPOCH_TIME } = require('@liskhq/lisk-constants');
const accounts = require('./accounts.json');

const getTimestamp = () => {
    // check config file or curl localhost:4000/api/node/constants to verify your epoc time (OK when using /transport/node/index.js)
    const millisSinceEpoc = Date.now() - Date.parse(EPOCH_TIME);
    const inSeconds = ((millisSinceEpoc) / 1000).toFixed(0);
    return parseInt(inSeconds);
};

let tx =  new RegisterPacketTransaction({
    asset: {
        packetId: accounts.packet.address,
        postage: `${transactions.utils.convertLSKToBeddows('5')}`,
        security: `${transactions.utils.convertLSKToBeddows('100')}`,
        minTrust: 0,
    },
    fee: '0',
    recipientId: accounts.recipient.address,
    timestamp: getTimestamp()
});

tx.sign(accounts.sender.passphrase); // 16313739661670634666L

console.log(tx.stringify());
process.exit(0);

View more ways to use @liskhq/lisk-transactions

@liskhq/lisk-transactions

@liskhq/lisk-transactions contain utility functions related to transactions according to the Lisk protocol

Installation

$ npm install --save @liskhq/lisk-transactions

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

@liskhq/lisk-transactions dependencies

@liskhq/lisk-codec @liskhq/lisk-cryptography @liskhq/lisk-validator

@liskhq/lisk-transactions development dependencies

@types/jest @types/jest-when @types/node @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint eslint-config-lisk-base eslint-plugin-import eslint-plugin-jest jest jest-extended jest-when prettier source-map-support ts-jest ts-node tsconfig-paths typescript

FAQs

What is @liskhq/lisk-transactions?

Utility functions related to transactions according to the Lisk protocol. Visit Snyk Advisor to see a full health score report for @liskhq/lisk-transactions, including popularity, security, maintenance & community analysis.

Is @liskhq/lisk-transactions popular?

The npm package @liskhq/lisk-transactions receives a total of 14,415 weekly downloads. As such, @liskhq/lisk-transactions popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @liskhq/lisk-transactions well maintained?

We found indications that @liskhq/lisk-transactions is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @liskhq/lisk-transactions safe to use?

The npm package @liskhq/lisk-transactions 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 2 November-2024, at 08:37 (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 (14,415)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @liskhq/lisk-transactions?

@liskhq/lisk-transactions

Installation

License

@liskhq/lisk-transactions dependencies

@liskhq/lisk-transactions development dependencies

FAQs

What is @liskhq/lisk-transactions?

Is @liskhq/lisk-transactions popular?

Is @liskhq/lisk-transactions well maintained?

Is @liskhq/lisk-transactions 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