Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/strvcom/dep-manager-web
Project Quality Tracker
https://github.com/strvcom/dep-manager-web
frontend github-oauth graphql netlify react
Last synced: 2 months ago
JSON representation
Project Quality Tracker
- Host: GitHub
- URL: https://github.com/strvcom/dep-manager-web
- Owner: strvcom
- License: mit
- Created: 2018-04-04T12:50:01.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2023-01-27T04:51:26.000Z (about 2 years ago)
- Last Synced: 2024-04-14T06:31:39.224Z (10 months ago)
- Topics: frontend, github-oauth, graphql, netlify, react
- Language: TypeScript
- Homepage: https://github.com/strvcom/dep-manager-web/projects/3
- Size: 4.19 MB
- Stars: 12
- Watchers: 18
- Forks: 1
- Open Issues: 30
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Project Quality Tracker
### Outline
As you make and maintain more projects over time, each of them depending on external, usually open-sourced libraries, it's easy to loose track of the quality of those dependencies. Security issues arise, new versions are released. Also, good practices evolve and take long to reach all projects.
Bida App aims to create a dashboard of project's health to manage outdate status for dependencies and compliance with good practices.
### Target Audience
#### Managers
- As a platform leader I would like to have a nice overview of our projects;
- I need to know which project are up-to-date and which are not;
- I would like to have an overview of libraries used across the organization;
- I would like to know if forbidden libraries are used. If so, on which projects;
- I would like to enforce some best practises across projects. For example by using [code-quality-tools](https://github.com/strvcom/code-quality-tools), TypeScript, or tests. By using Bida App I can easily explore which project do not comply to our best practises.
#### Developers
- Simple way to explore what kind of libraries we are using across projects.
- Easily find if a library is in use elsewhere, and who could help me with that;
- Find troubleshooting for libraries on specific version.
- Find issues with dependencies before they go live;
- Explore library trends and usage history within organization.
## Table of Contents
- [Workflow](docs/00-flow.md#workflow)
- [1. Create issues](docs/00-flow.md#1-create-issues)
- [2. Backlog](docs/00-flow.md#2-backlog)
- [3. Ready for dev](docs/00-flow.md#3-ready-for-dev)
- [4. In progress](docs/00-flow.md#4-in-progress)
- [5. Approval](docs/00-flow.md#5-approval)
- [6. Done](docs/00-flow.md#6-done)
- [Stack & Whys](docs/01-stack.md#stack--whys)
- [Built with](docs/01-stack.md#built-with)
- [Decisions](docs/01-stack.md#decisions)
- [Why netlify](docs/01-stack.md#why-netlify)
- [Why GraphQL](docs/01-stack.md#why-graphql)
- [Why Apollo](docs/01-stack.md#why-apollo)
- [Why npms](docs/01-stack.md#why-npms)
- [Development Guidelines](docs/02-development.md#development-guidelines)
- [Getting started](docs/02-development.md#getting-started)
- [Isolated environments](docs/02-development.md#isolated-environments)
- [Environment Variables](docs/02-development.md#environment-variables)
- [Version control](docs/02-development.md#version-control)
- [Branch](docs/02-development.md#branch)
- [Commit](docs/02-development.md#commit)
- [Integration](docs/02-development.md#integration)
- [Issue vs Pull-Request redundancy](docs/02-development.md#issue-vs-pull-request-redundancy)
- [Rebase and merge](docs/02-development.md#rebase-and-merge)
- [Alternative Softwares](docs/03-alternatives.md#alternative-softwares)
- [snyk](docs/03-alternatives.md#snyk)
- [Libraries.io](docs/03-alternatives.md#librariesio)
- [Probe.ly](docs/03-alternatives.md#probely)
- [Greenkeeper](docs/03-alternatives.md#greenkeeper)