Project60 / Project60/org.project60.banking
Security Review / Audit
Open
Nobody has claimed this yet.
enhancement
feature
- Dominant language
- PHP
- Stars
- 22
- Forks
- 45
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 7
Description
Before releasing this to the public, there should be a security audit. Some thoughts:
- data protection / privacy
- SQL injection
- code injection
- ...
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points, so begin by surveying the PHP extension and its release surface. Define an audit covering data protection and privacy, SQL injection, and code injection; done requires the audit to be completed and its findings recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100