
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@bam.tech/danger-plugin-todo
Advanced tools
Address your technical dept at some point
This package is more or less a fork from danger-plugin-fixme
from @zetaron, licensed under MIT.
Install:
yarn add @tychot/danger-plugin-todo --dev
At a glance:
// dangerfile.js
import { schedule } from "danger";
import todo from "@tychot/danger-plugin-todo";
schedule(todo());
See the GitHub release history.
See CONTRIBUTING.md.
FAQs
Address your technical dept at some points
The npm package @bam.tech/danger-plugin-todo receives a total of 2 weekly downloads. As such, @bam.tech/danger-plugin-todo popularity was classified as not popular.
We found that @bam.tech/danger-plugin-todo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 10 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
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.