This repository is a historical student-work archive, not production software. Its projects are preserved for evidence, study, and portfolio review and do not have supported release branches or security-maintenance guarantees.
Old dependency findings and insecure historical patterns may be documented rather than upgraded. A vulnerability in archived student code does not automatically receive a compatibility fix, especially when changing it would erase the historical record.
Please report any of the following privately:
- accidentally included credentials, tokens, keys, or connection strings;
- personal, student, customer, or other restricted data;
- unsafe or unexpectedly executable downloads;
- security-sensitive evidence that should not be public;
- third-party material that may have been included without permission; or
- a weakness in the archive tooling, website data, or current publication process that could affect visitors.
Use GitHub's Report a vulnerability option for this repository. If that option is unavailable, contact Codie Shannon through the portfolio contact channel without posting the sensitive details publicly.
Do not open a public issue containing credentials, personal data, exploit details, or links to material that should be removed.
A report will be assessed for present-day risk and archive integrity. Possible responses include removing or redacting material, invalidating a release, rewriting affected Git history when necessary, repairing archive tooling, or adding clearer historical warnings. Legacy application vulnerabilities may instead be documented as accepted historical limitations.
No response time or remediation deadline is guaranteed for the archived projects.
Widows Suite has a documented historical security-tool finding. The Defender-detected original file is not included in this public archive. Downloads, credential-like content, and sensitive evidence are also excluded. The archive does not claim that the quarantined original file was malware-free.
Use isolated development environments, synthetic data, and loopback-only services when following the reproduction index. Do not supply real credentials or personal datasets. Review old dependency trees before allowing network access or using them outside a disposable audit environment.