-
-
Notifications
You must be signed in to change notification settings - Fork 476
Issues: composer/packagist
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Should have one page dedicated to explaining reasons for "no delete, no forks, no testing"
Easy pick
Feature
UX
#113
opened Mar 8, 2012 by
simensen
[feature request] Add more repository info for package view.
Easy pick
Feature
#216
opened Sep 6, 2012 by
desarrolla2
Projects deleted from GitHub should be removed from Packagist
Feature
#237
opened Oct 16, 2012 by
simensen
[feature request] Support for packages not in VCS to be handled by packagist.org
Feature
#270
opened Jan 13, 2013 by
njh
By default hide in search results packages without stable version to encourage proper versioning
Feature
UX
#300
opened Mar 23, 2013 by
turneliusz
Security -- how are malicious or insecure Packagist packages reported
Feature
#335
opened Jul 10, 2013 by
ghost
Report packages as not "currently no response from maintainer" / "maybe deprecated"
#600
opened Oct 28, 2015 by
ghost
Can't update a gitlab-hosted repository (composer.json reportedly invalid)
Support
#639
opened Jan 21, 2016 by
wernerdweight
[Secure Code Delivery] Stream Updates to a Chronicle
Feature
#797
opened Jul 9, 2017 by
paragonie-scott
Previous Next
ProTip!
Follow long discussions with comments:>50.