Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@metamask/slip44
Advanced tools
Readme
A simple mapping between SLIP-44 identifiers and the associated metadata, parsed directly from the repository linked above.
yarn add @metamask/slip44
or
npm install @metamask/slip44
const slip44 = require('@metamask/slip44');
const metadata = slip44['0'];
assert.equals(metadata.name, 'Bitcoin');
type Slip44 = {
[index: string]: {
index: string;
hex: `0x${string}`;
symbol: string;
name: string;
};
};
nvm use
will automatically choose the right node version for you.yarn install
to install dependencies and run any required post-install scriptsTo fetch the current SLIP-44 specification and re-generate the exported data, run yarn rebuild
.
Note that the yarn build
command simply rebuilds the JSON file from the raw Markdown committed to this repository.
yarn rebuild
re-fetches the markdown (via yarn fetch
) and then runs yarn build
.
Run yarn test
to run the tests once. To run tests on file changes, run yarn test:watch
.
Run yarn lint
to run the linter, or run yarn lint:fix
to run the linter and fix any automatically fixable issues.
The project follows the same release process as the other libraries in the MetaMask organization. The GitHub Actions action-create-release-pr
and action-publish-release
are used to automate the release process; see those repositories for more information about how they work.
1.x
for a v1
backport release).v1.0.2
release, you'd want to ensure there was a 1.x
branch that was set to the v1.0.1
tag.workflow_dispatch
event manually for the Create Release Pull Request
action to create the release PR.action-create-release-pr
workflow to create the release PR.yarn auto-changelog validate --rc
to check that the changelog is correctly formatted.action-publish-release
workflow to tag the final release commit and publish the release on GitHub.publish-release
GitHub Action workflow to finish. This should trigger a second job (publish-npm
), which will wait for a run approval by the npm publishers
team.publish-npm
job (or ask somebody on the npm publishers team to approve it for you).publish-npm
job has finished, check npm to verify that it has been published.FAQs
A simple mapping between slip44 IDs and their network metadata.
The npm package @metamask/slip44 receives a total of 8,248 weekly downloads. As such, @metamask/slip44 popularity was classified as popular.
We found that @metamask/slip44 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 12 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.