
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@kiltprotocol/prototype-sdk
Advanced tools
The KILT SDK is a collection of classes and methods that application developers can utilize to interact with the KILT Network. The SDK is provided in Typescript.
Read the getting started guide, or browse the API documentation.
Edit your ~/.npmrc
and insert/add kiltbot's auth token to the registry
e.g. //registry.npmjs.org/:_authToken=8...
Use within your project with yarn add @kilt/prototype-sdk
You can use different SDK branches or versions, by linking it into your projects locally.
Execute yarn link
in the SDK and copy the command in the output, which should look like this:
yarn link "@kiltprotocol/prototype-sdk"
Go into your project folder and execute that second command.
The SDK is now symlinked in your projects node_modules
folder
Before you see your changes from the SDK, you have to build it, by executing yarn build
.
Execute yarn unlink "@kiltprotocol/prototype-sdk"
in the project folder.
After that execute yarn install --check-files
to get the version from the registry back.
Deployment is triggered by a push to the master branch as a result to a release build.
To build a release, start the release build job for the SDK in AWS CodeBuild. See here for more info on building releases.
As a result of a release build, a new version of the SDK is published to the NPM registry.
Note: Don't forget to reference the correct version in the client and services
Test coverage does not seem to be fail in all cases, except for testWatch.
If the prototype sdk build fails on AWS, please check the error log. Usually it says
npm ERR! publish Failed PUT 403
npm ERR! code E403
npm ERR! You cannot publish over the previously published versions: 0.0.3. : @kiltprotocol/prototype-sdk
This is on purpose as a new push to master branch triggers a build, but should not automatically and unintended release a new version.
Please update package.json's version in order to publish a new version to the registry by AWS after pushing to master.
FAQs

The npm package @kiltprotocol/prototype-sdk receives a total of 0 weekly downloads. As such, @kiltprotocol/prototype-sdk popularity was classified as not popular.
We found that @kiltprotocol/prototype-sdk demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.