Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
@spinnaker/kayenta
Advanced tools
[![Build Status](https://travis-ci.org/spinnaker/deck-kayenta.png?branch=master)](https://travis-ci.org/spinnaker/deck-kayenta)
In order to commit to this repo, please fork the repository and submit Pull Requests from a fork rather than a branch. It requires additional permissions to push branches.
Make sure that node and yarn
are installed on your machine. The minimum versions for each are listed in package.json
.
To develop this module, run it as a Deck dependency using either yalc
(recommended) or npm link
.
In the root of this repository and the main Deck repository, run
yarn
Globally install yalc.
From the root of this repository, run
yalc publish
From the root of the main Deck repository, run
yalc add @spinnaker/kayenta
yarn start
As you make additional changes in this repository, run
yalc publish --push
From the root of this repository, run
npm link
From the root of the main Deck repository, run
npm link @spinnaker/kayenta
You should only have to run these commands once.
Next, run WATCH=true yarn lib
at the root of this repository. In a separate terminal,
run yarn start
at the root of the main Deck repository.
deck-kayenta
uses feature and development flags. These are fully configurable within settings.js
,
but it is usually easier to pass the flags as environment variables.
These are good defaults:
REDUX_LOGGER=true \
API_HOST=http://localhost:8084 \
METRIC_STORE=stackdriver \
CANARY_STAGES_ENABLED=true \
TEMPLATES_ENABLED=true \
yarn start
This module is published as an NPM package.
package.json
's patch version - e.g., to 0.0.57
.package.json
's version, e.g., v0.0.57
. @spinnaker/kayenta
will be automatically published to NPM.Once @spinnaker/kayenta
has been published, the Deck dependency on deck-kayenta will be automatically
updated by Dependabot. Keep an eye out
for a PR against Deck from Dependabot.
To run deck-kayenta
's tests, run yarn test
.
To run deck-kayenta
's tests and generate a code coverage report, run yarn test-coverage
.
Open /coverage/html/index.html
in a browser to view the HTML version of the report.
FAQs
![Branch Build](https://github.com/spinnaker/deck-kayenta/workflows/Branch%20Build/badge.svg)
The npm package @spinnaker/kayenta receives a total of 46 weekly downloads. As such, @spinnaker/kayenta popularity was classified as not popular.
We found that @spinnaker/kayenta demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.