vet
PRevent
| vet | PRevent | |
|---|---|---|
| 17 | 5 | |
| 523 | 226 | |
| 25.6% | 1.8% | |
| 9.3 | 9.0 | |
| 5 days ago | 4 months ago | |
| Go | Python | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vet
-
Ask HN: What Are You Working On? (June 2025)
I am working on a next-gen software composition analysis tool that can identify malicious open source packages through code analysis. Adopts a policy as code (CEL) approach to build security guardrails against risky OSS components using opinionated policies.
GitHub: https://github.com/safedep/vet
- Vet MCP: Software Composition Analysis for AI Code Editors
-
Malicious npm Package Impersonating Popular Express Cookie Parser
Our free and open source tool vet is integrated with the SafeDep Cloud Package Scanning Service and can be used to detect malicious packages before they are installed. vet-action is a GitHub Action that can be used to establish proactive guardrails against malicious open source packages in your GitHub Actions workflows.
-
How to Effectively Vet Your Supply Chain for Optimal Performance
Explore about SafeDep on GitHub - https://github.com/safedep/vet
-
Ask HN: How are you acquiring first 100 users?
Not sure if it’s relevant because you specifically mentioned about B2C.
For cyber security product, we took the open source route. We build our core technology in public as open source project.
https://github.com/safedep/vet
The commercial SaaS is for scaling and management. Our entire funnel is based on OSS. Folks who have already found value and is looking to scale their deployment.
This model works for us especially at our current stage where we are 100% engineering led.
-
Show HN: MCP-Shield – Detects security issues in MCP servers
May be try out vet as well: https://github.com/safedep/vet
vet is backed by a code analysis engine that performs malicious package (npm, pypi etc.) scanning. We recently extended it to support GitHub repository scanning as well.
It found the malicious behaviour in mcp-servers-example/bad-mcp-server.js
-
Agentic Analysis of Open Source Package Code for Malware
➡️ https://github.com/safedep/vet
-
Scanning Open Source Packages for Malicious Code 🚨
Malicious code in open sources is real and people get hacked due to it as we have seen with changed-files incident, ultralytics hack and multiple such incidents. vet now supports identification of malicious OSS packages through active code analysis.
- Show HN: Scan GitHub Actions for Malicious Code
-
Popular GitHub Action tj-actions/changed-files is compromised
I think the conventional approach of checking for vulnerabilities in 3rd party dependencies by querying CVE or some other database has set the current behaviour i.e. if its not vulnerable it must be safe. This implicit trust on vulnerability databases has been exploited in the wild to push malicious code to downstream users.
I think we will see security tools shifting towards "code" as the source of truth when making safety and security decision about 3rd party packages instead of relying only on known vulnerability databases.
Take a look at vet, we are working on active code analysis of OSS packages (+ transitive dependencies) to look for malicious code: https://github.com/safedep/vet
PRevent
-
Popular GitHub Action tj-actions/changed-files is compromised
We've recently released open-source tools that would have easily prevented this, before anything runs or added to any pipeline:
1. The maintainers could have used PRevent to immediately alert and block any PR containing malicious code, or easily configured it for detection in case of a direct push: https://github.com/apiiro/PRevent
2. Users could have used our malicious code detection ruleset to immediately detect and block it when scanning updates in all relevant CI/CD stages: https://github.com/apiiro/malicious-code-ruleset
3. For a better understanding of the detection, the malicious code falls precisely into the patterns presented in our research: https://apiiro.com/blog/guard-your-codebase-practical-steps-...
-
Tj-actions/changed-files GitHub Action Compromised – used by over 23K repos
https://github.com/apiiro/PRevent
2. Users could have used our malicious code detection ruleset to immediately detect and block it when scanning updates in all relevant CI/CD stages:
-
I built a PR listener and a ruleset for detecting malicious code at any stage of the CI/CD
The app, PRevent - https://github.com/apiiro/PRevent
- Show HN: I built a PR listener and ruleset to detect malicious code in CI/CD
- Show HN: Malicious Code Detector
What are some alternatives?
solarsploit - Red team tool that emulates the SolarWinds CI compromise attack vector.
malicious-code-ruleset - Focused malicious code detection ruleset, with a high protection-to-noise ratio
cnspec - An open source, cloud-native security to protect everything from build to runtime
gitapp_alert_on_public - A service for finding and alerting on newly created public repositories for GitHub users who are part of a GitHub organization.
scorecard - OpenSSF Scorecard - Security health metrics for Open Source
changed-files - Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories. Secure drop-in replacement for tj-actions/changed-files.