Create tool to rate the good practice and compatibility of an app
Open
Nobody has claimed this yet.
- #61732 by @copilot-swe-agent — closed without merging
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Whether the app has:
- autoloader
- certain dependencies like
nextcloud/ocp - cs-fixer
- psalm
- rector
- composer-bin
- vue3
- playwrights
- NC version compatibility
- SBOM
- REUSE
- dependency version vs server dependency version
- php version
- release-relay workflow
- automated source code scan when uploading an app to check for deprecated API usages
- screenshot automation
- dist-build workflow
- build and publish workflow https://github.com/nextcloud/twofactor_admin/actions/workflows/appstore-conventional-build-publish.yml
- dependabot + npm-audit
- Real maintenance of compatibility with newer server versions
- regular server versions bumping in metadata (as opposed to one-time max-version="99"): yes
- commits other than versions bumping (bots excluded): yes
- release rate: frequent (changelog)
- Sustainability (and how contribute to it)
- development activity: really active
- more than 1 active developer: yes
- main dependencies health
- backed by an organisation
- QA
- issues: more solved than unresolved ones (although really high number of them)
- project management: kanban and milestones
- User friendliness
- documentation
- user: yes
- admin: yes
- developer: yes
- support: community and also commercial available
- localization: continuous
- Miscellaneous
- Mobile and desktop companion apps (and health of their development)
- App store flag for apps to signal technology implementation
- Governance/eDiscovery
- User id change
- Unify sharing
- Audit log
- Zero down time
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the app-store workflow at .github/workflows/appstore-conventional-build-publish.yml and the linked issue context. Define the scope and data sources for the proposed checks, then confirm that the tool can produce ratings for the listed practices and expose the requested app-store technology flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php, playwright
- Domain
- devops, release, testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100