Dependency and code review
Review product code and third-party dependencies for defects, unsafe defaults and known vulnerabilities before changing them.
Trust / Security practice
Careful work. Clear boundaries.
Security is part of building useful software. This page defines the scope and principles of the practice, with published policies and a direct reporting contact.
01 / Scope and review
The software we own.
Application security
Evaluate the websites and software we own. External systems require explicit authorisation from their owner.
Patch validation
Check a fix against the issue it addresses, and verify the relevant product behaviour before release.
Human accountability
Model-assisted analysis is input to an engineering decision. The founder remains accountable for changes and published claims.
Coordinated disclosure
Handle reports about our own systems under the published policy. Report third-party defects to their responsible vendor.
Permission comes before testing.
The practice covers Technical Dost’s own product code, dependencies and infrastructure. Testing a third-party system requires its owner’s written authorisation and an agreed scope.
The acceptable use policy defines prohibited activities. The disclosure policy describes permitted good-faith research on our systems and the reporting process.
Read the acceptable use policyA direct route for a report.
Send reports to support@technicaldost.com. The policy sets a response target of 72 hours and a coordinated disclosure window of 90 days, subject to its terms.
For any provider program with restricted access, applications follow that provider’s own verification process. This site does not claim acceptance into a model-access program or security certification.