
Security News
TeamPCP and BreachForums Launch $1,000 Contest for Supply Chain Attacks
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.
@kepler-io/core-common
Advanced tools
This project represents the Kepler common library. This library is sharing logic related to multiple libraries. Shared logic.
This project represents the Kepler common library. This library is sharing logic related to multiple libraries. Shared logic.
Run yarn build.
Kepler Common Lib is installable as NMP Module: npm install @kepler-io/core-common.
Upgrade of package is available via command: npm upgrade @kepler-io/core-common
You can test packaging locally via npm pack and observe generated tar file.
Publishing is done via NPM (not Yarn): npm run publish-remote.
In order for your publish to be successfull you must increment the version on the package.json file following the instructions below:
Given a version number MAJOR.MINOR.PATCH, increment the:
You can test your local features using a pre-release version, following the rules below:
Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.–.
FAQs
This project represents the Kepler common library. This library is sharing logic related to multiple libraries. Shared logic.
We found that @kepler-io/core-common demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 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
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.

Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.

Research
GemStuffer abuses RubyGems as an exfiltration channel, packaging scraped UK council portal data into junk gems published from new accounts.