no-leaks
:potable_water: PHPUnit Plugin for detecting Memory Leaks in code and tests (by Roave)
SecurityAdvisories
:closed_lock_with_key: Security advisories as a simple composer exclusion list, updated daily (by Roave)
no-leaks | SecurityAdvisories | |
---|---|---|
1 | 6 | |
496 | 2,648 | |
0.6% | 0.5% | |
8.8 | 9.6 | |
4 days ago | 8 days ago | |
PHP | ||
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
no-leaks
Posts with mentions or reviews of no-leaks.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-22.
-
PHP libraries and tools
roave/no-leaks: PHPUnit Plugin for detecting Memory Leaks in code and tests
SecurityAdvisories
Posts with mentions or reviews of SecurityAdvisories.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-11.
-
Preventing Installing Composer Dependencies with Known Security Vulnerabilities
To reduce the chance of introducing vulnerable dependencies into your projects, you can use tools such as "Roave Security Advisories" (roave/security-advisories).
- With the recent scandal over the 'node-ipc' package, is Composer also vulnerable like this? Is there any security measure in the Composer to prevent this type of attack?
- Open source is not a place for politics
-
Composer conflict, how can we use it?
In order to avoid accepting third-party code with well-known security issues you can take advantage of SecurityAdvisories by Roave, a library which uses conflict as shown in this article to block unsafe packages. Give it a look!
-
PHP libraries and tools
roave/security-advisories: Security advisories as a simple composer exclusion list, updated daily
-
Laravel QR Code Generator Infected with Malware
Every composer user should use at least https://github.com/Roave/SecurityAdvisories
What are some alternatives?
When comparing no-leaks and SecurityAdvisories you can also consider the following projects:
PHPStan - PHP Static Analysis Tool - discover bugs in your code without running it!
local-php-security-checker - PHP security vulnerabilities checker
ParaTest - :computer: Parallel testing for PHPUnit
enlightn - Your performance & security consultant, an artisan command away.
Serializer - Library for (de-)serializing data of any complexity (supports JSON, and XML)
Psalm - A static analysis tool for finding errors in PHP applications
ruby-advisory-db - A database of vulnerable Ruby Gems
composer-unused - Show unused composer dependencies by scanning your code
Deptrac - Keep your architecture clean.
Spout - Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way
no-leaks vs PHPStan
SecurityAdvisories vs local-php-security-checker
no-leaks vs ParaTest
SecurityAdvisories vs enlightn
no-leaks vs Serializer
SecurityAdvisories vs PHPStan
no-leaks vs Psalm
SecurityAdvisories vs ruby-advisory-db
no-leaks vs composer-unused
SecurityAdvisories vs Deptrac
no-leaks vs Spout
SecurityAdvisories vs Serializer