Payment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.
Example result
Code review: Python order-import script for a small online shop
What the code does
- Reads
orders.csvfrom the shop export. - For each order line, finds the product by SKU in
stock.xlsxand subtracts the quantity. - Writes the updated stock back and logs totals to
import_log.txt.
The structure is clear and functions are well named. Most issues are about input that does not look the way the script expects.
Bugs and weak spots
| # | Line | Severity | Issue |
|---|---|---|---|
| 1 | 48 | High | The same CSV can be imported twice; there is no check for already processed order IDs. This is the most likely cause of negative stock. |
| 2 | 72 | High | int(row["qty"]) crashes on empty or "2.0" values from refunded orders. |
| 3 | 95 | Medium | SKU lookup is case-sensitive: "gt-101" and "GT-101" are treated as different products. |
| 4 | 130 | Medium | The file is opened without encoding="utf-8", so product names with accents break on Windows. |
| 5 | 201 | Low | Bare except: hides real errors and makes the log useless. |
Corrected fragments
Issue 1: skip orders already imported
processed = load_processed_ids("processed_orders.txt")
for row in reader:
if row["order_id"] in processed:
continue
# ... existing logic ...
processed.add(row["order_id"])
save_processed_ids("processed_orders.txt", processed)
Why: each order is applied once, even if you run the script on the same file again.
Issue 2: read quantity safely
raw = (row.get("qty") or "").strip()
try:
qty = int(float(raw))
except ValueError:
log.warning("Order %s: bad quantity %r, skipped", row["order_id"], raw)
continue
Why: refunded or partial lines are skipped with a clear note instead of stopping the whole import.
Issue 3: normalise SKUs
sku = row["sku"].strip().upper()
Apply the same .strip().upper() when building the stock dictionary.
Style and readability
process()is 90 lines long; split it intoread_orders,apply_to_stock,write_report.- Replace magic column numbers (
row[7]) with header names.
Please test each fix on a copy of your files: we read the code but did not run it.
Client: owner of a tea shop who wrote a 310-line Python script that imports orders from a CSV export into the stock spreadsheet Problem reported: "Sometimes stock goes negative, and the script crashes on some files."
The client and all details are made up.
About this service
Many security holes are visible right in the code: SQL or shell commands built from user input, output printed without escaping, passwords stored with a fast hash, checks that confirm who the user is but not what they may access, and keys written into the source. We read your code with the OWASP Top 10 as a checklist, explain each weak spot and how it could be abused, and rank them by risk. Each finding comes with a corrected fragment using the safe pattern for your language.
What is included
- What you getA written review on the order page: weak spots ranked by risk with an explanation of each, and corrected fragments using safe patterns. Premium adds a short hardening checklist for the rest of the project.
- InjectionSQL, shell and template injection
- Escaping outputCross-site scripting risks
- Access checksWho can see and change what
- Passwords and secretsHashing and keys out of code
- Ranked findingsFix the worst first
How it works
- 1BriefYou paste the sensitive parts of the code
- 2ReadingWe check it against OWASP Top 10
- 3ReviewYou get ranked findings and fixes
What we need from you
The code that handles input, logins, files or payments pasted as text or screenshots with secrets replaced by placeholders, the language and framework, and who uses the app.
We will ask you:
- Which language and framework?
- Which parts handle user input, logins or payments?
- Who uses the app?
- Has a specific incident or warning prompted this review?
Compare packages
| Packages | BasicCode up to 100 lines$15 | StandardCode up to 400 lines$35 | PremiumUp to 1,000 lines with a hardening checklist$69 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 3 days |
| Revisions | 1 | 2 | 3 |
| Lines of code | up to 100 | up to 400 | up to 1,000 |
| Corrected fragments | Yes | Yes | Yes |
| Hardening checklist | No | No | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Is this a penetration test or a security certificate?
No. We read the code you send and do not attack or scan your live system, so this does not replace a formal audit where one is required.
Should I send passwords or keys?
Never. Replace them with placeholders; if a real key was already in the code, rotate it.
Do you run my code?
No. We read it carefully and reason about how it behaves, but we do not execute it, so test every suggested fix in your own project.