Composer packages from private Satis repository not recognised

Satis (https://getcomposer.org/doc/articles/handling-private-packages-with-satis.md) is used for hosting private repositories. The repository is typically protected with basic auth, which composer detects, asks the user for input and caches.

Our current use case for a Satis repository to curate wordpress pro plugins (and keep API keys out of composer.json/lock).

VersionEye could parse composer.json/lock for repositories other than packagist, allow entry of basic auth credentials, cache these then hit the private repository to see if packages have changed.

VersionEye currently shows these packages as unknown.

Comments (0)