Roave / SecurityAdvisories

:closed_lock_with_key: Security advisories as a simple composer exclusion list, updated daily
MIT License
2.7k stars 105 forks source link

package still relevant after composer audit ? #112

Closed Jimbolino closed 1 year ago

Jimbolino commented 1 year ago

I recently noticed all my composer update started to give a message: No security vulnerability advisories found

After reading some documentation about it: https://php.watch/articles/composer-audit

packagist.org, the main source of package metadata of Composer, now has a new API that returns a list of reported security vulnerabilities for a given list of package names. Packagist routinely fetches the vulnerability information from Github Security Advisories and FriendsOfPHP/security-advisories repository.

Since this repo also uses the same FriendsOfPHP/security-advisories source, is it still really relevant ?

Ocramius commented 1 year ago

To some extent: this package will implicitly aid composer update in picking secure dependency ranges.

As for composer require --dry-run roave/security-advisories, I'd say that composer audit gives you much better ergonomics.

Ocramius commented 1 year ago

Note: regardless of what the community will pick, this package will stay maintained long-term.