peternijssen/packy

Packy is an open source tool to validate if your dependencies are up 2 date. Packy is based on the Symfony framework.

Hi there 👋

I'm Peter, Former CTO and Product Manager at CMNTY Corporation and now working as Managing Consultant at inQdo. All work in my Github repositories is on personal level.

📈 GitHub Stats

packy's Issues

Integrate composer analyzer

Integrate a composer analyzer which analyzes if composer packages are up 2 date

Implement role system

There should be 3 roles:

• Admins
• Users
• Observers

Admins can manage projects and users
Users can manage projects
Observers can only view projects, but not manage them

Integrate Gitlab repository

Integrate gitlab repository, so versions can also be retrieved from gitlab repositories

Demo site home page is broken

Hello,
When I tried to log in to the Demo page at https://packy.peternijssen.nl with username password as demo / demo it gave a symphony exception and did not log in as well.

Show graphs on analyze page

A couple of nice graphs should be displayed on the project analyze page, showing you quickly what the current status is.

Check composer against security advisory

We should check the composer file against the security advisory of SensioLabs;
https://security.sensiolabs.org/

Perhaps other package vendors also have a similar system.

Implement authentication system

An authentication system should be implemented; https://github.com/FriendsOfSymfony/FOSUserBundle
You should need to login, before entering Packy. Registration is disabled, but users can be created in the admin section.

Filter branches

You should be able to select branches which you want to analyze. Branches should be loaded and shown in a list to choose from.

Implement caching mechanism

Retrieving versions from repositories should be cached for a couple of hours, until the next check is being run. This way, traffic to repositories like Github is lower and analysis run faster.

Login with Gitlab

You should be able to login with a Gitlab account. You can then define which projects should be analyzed by Packy.

Show stats on project overview page

Stats per project should be shown on the project overview. Perhaps some graphs or numbers.

Handle private repositories

Private repositories cannot be analyzed currently. Neither can we get the latest version of packages. We should find a way to authorize Packy to get access to these repositories.

Integrate bower analyzer

Integrate a bower analyzer which analyzes if bower packages are up 2 date

Login with github

You should be able to login with a Github account. You can then define which projects should be analyzed by Packy.

Integrate Bitbucket repository

Integrate bitbucket repository, so versions can also be retrieved from bitbucket repositories