
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
@brigadecore/brigade-sdk
Advanced tools
 [](https://kubernetes.slack.com/messages/C87MF1RFD)
This is a Brigade 2-compatible SDK for JavaScript and TypeScript.
Great care has been taken to ensure this SDK works within recent versions of Node as well as modern browsers (latest versions of Firefox, Chrome, Edge, Safari, etc.) if properly transpiled with webpack or similar.
Install into your project using your favorite package manager.
For instance:
$ npm install --save @brigadecore/brigade-sdk
Or:
$ yarn add @brigadecore/brigade-sdk
Note: All examples that follow use TypeScript.
A Brigade API client can be obtained as follows:
import { APIClient } from "@brigadecore/brigade-sdk"
// ...
const client = new APIClient(apiAddress, apiToken, opts)
In the example above, it is assumed:
apiAddress
points to a Brigade 2 API server. The address must include the
protocol (i.e. must be prefixed with http://
or https://
).apiToken
is:
opts
, as one might infer, is an optional parameter. If included, it must be
an object, which may have a single field allowInsecureConnections
containing
the value true
or false
to indicate whether SSL errors should be tolerated
by the client. If not specified, SSL errors will not be tolerated. This
option is only applicable when the value of the apiAddress
argument uses
https://
as the scheme.The client
returned from the call to the new APIClient(...)
constructor is
the root in a tree of more specialized clients.
To obtain a client for working with the "core" components of Brigade (Projects, Events, etc.):
const coreClient = client.core()
The coreClient
permits navigation to even more specialized clients, for
example:
const projectsClient = coreClient.projects()
If your program needs to interact with only a specific subset of the Brigade API, it is possible and encouraged to directly instantiate just the specific subset of the client tree that is needed.
For instance, this example shows instantiation of only the Events client-- something that might be practical for a program such as a Brigade gateway, whose only interaction with Brigade involves the creation of new Events:
import { core } from "@brigadecore/brigade-sdk"
// ...
const eventsClient = new core.EventsClient(apiAddress, apiToken, opts)
The arguments passed above are the same as in our initial example.
Working Node and browser-based examples are available in the examples directory.
The Brigade project accepts contributions via GitHub pull requests. The Contributing document outlines the process to help get your contribution accepted.
We have a slack channel! Kubernetes/#brigade Feel free to join for any support questions or feedback, we are happy to help. To report an issue or to request a feature open an issue here
Participation in the Brigade project is governed by the CNCF Code of Conduct.
FAQs
 [](https://kubernetes.slack.com/messages/C87MF1RFD)
The npm package @brigadecore/brigade-sdk receives a total of 428 weekly downloads. As such, @brigadecore/brigade-sdk popularity was classified as not popular.
We found that @brigadecore/brigade-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.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.