Supported stacks
- .NET / ASP.NET Core / worker services
- Node / TypeScript / Express / NestJS
- React / Next.js / Remix
Supported stacks
Check whether Shipward can work with your repo and stack
Shipward keeps the technical boundary explicit so the audit and any follow-on work can stay credible from the start.
Source intake and scope boundaries
- GitHub repository access is the default intake path for connected source.
- Approved .zip archive intake is available when a repository handoff is not practical.
- One primary repository is the default audit scope.
- Archive uploads should stay under 250 MB.
- Working trees should stay under 1 GB, 25,000 files, and 300,000 lines of code.
- Up to three deployable apps or services can be assessed inside the standard brochure scope.
Standard exclusions
- No direct production deployment into customer environments is promised from the brochure surface.
- No ongoing support, retainer, managed service, subscription, or formal SLA is included unless separately agreed.
- No unsupported-stack rescue promise is made before source preflight confirms fit.
- No default handling of credentials, production data or logs, employee personal information, customer end-user personal information, or regulated/sensitive data.
If your situation is close but not cleanly inside scope
Use the contact page when the repo shape, stack mix, or data-handling boundary needs manual review before an audit is commissioned.
Shipward would rather confirm fit early than take money for a scope that will not hold up under review.