Legacy Software Project Acquisition

@melopgabriel

Hello, Primary risk is accepting repositories that lack authentic commit history, meaningful human-driven bug fixes, and clear commercial transfer rights. I focus first on provenance: commit timelines, contributor diversity, timestamp consistency, and artifact traces (builds, CI configs, issue threads) to identify fabricated or AI-generated histories and quantify authenticity risk for COBOL, Fortran, RPG, .NET Framework / Classic ASP / VB6 / Legacy C#, Java 7 & earlier, C/C++, Go, Rust, Ruby, Swift, and Kotlin stacks. I have 12+ years working with long-running enterprise applications and migrations across legacy stacks including COBOL modernization into .NET and containerized C/C++ services, historic Java maintenance, and Legacy C# remediation. I have performed private-repo due diligence for acquisitions: audit reports that enumerate LOC, commit graphs, contributor counts, PR/issue fidelity, commercial licensing gaps, and a realistic remediation cost estimate. I will reference repository characteristics rather than public links during initial conversations. My first step is a targeted provenance audit: read-only access to the private repository plus metadata export (git log, fs tree, CI artifacts, tags) to produce a one-page authenticity score and a short list of ownership/license gaps. That audit takes 2–4 business days depending on repo size. - Do you prefer an initial non-disclosure review with a signed NDA or a direct read-only access link to the private repository? - Which technology stacks and approximate repo ages do you have available first for the provenance audit? Feel free to reach out if you want to talk through next steps. @melopgabriel

@danielv2801

Hello, how is it going? I understand you are specifically looking for privately owned legacy enterprise repositories with genuine long-term development history, substantial business logic, and verifiable human-maintained activity. I don’t want to misrepresent a repository or provide synthetic/demo code as a match, so I would only submit a codebase where ownership, development history, and commercial transfer rights can be properly verified. For any qualifying repository, I can provide the requested metadata including technology/version history, development period, business domain, approximate LOC, contributors, commits, PRs/issues, architecture migrations, ownership, and licensing status before granting access. Could you confirm whether repositories with confidential business logic can be evaluated under an NDA before the full codebase or repository history is disclosed? Looking forward to working with you.

@shaynegg

Hi, I like this project because acquiring a real legacy codebase requires more than matching a technology stack—the development history, ownership, and business logic need to be genuine and verifiable. I have hands-on experience working with older enterprise applications, including C#, .NET, Java, C/C++, and database-heavy systems, with maintenance, bug fixes, integrations, and modernization work. I can provide metadata first: stack/version, age, domain, LOC, contributors, commits, PR/issues, architecture history, ownership and commercial transfer rights. I understand you need private repositories with authentic human development history, not samples or synthetic projects. A useful first step is a structured repository audit so you can verify provenance and licensing before receiving full access. I can share matching projects privately for review.