NotY Game Repacker is designed for packaging files that the user legitimately owns or possesses.
The project does not implement:
- DRM bypass
- license bypass
- activation bypass
- launcher bypass
- ownership bypass
- destructive anti-debugging
- security-software bypassing
The current development stage does not implement cryptography.
There is therefore no claim that current packages provide encryption, authenticated encryption, or cryptographic confidentiality.
Do not describe an unfinished security mechanism as implemented.
Package integrity is a planned part of the architecture.
A future implementation should be able to detect problems such as:
- missing package data
- malformed package structure
- invalid metadata
- incomplete chunks
- modified payloads
- invalid installed files
The exact integrity algorithm is not declared final until implemented and tested.
If cryptographic protection is added later, the project should prefer a Windows-provided cryptographic implementation rather than inventing a weak custom primitive.
The implementation must document:
- algorithms
- key handling
- authentication behavior
- failure behavior
- version compatibility
- test coverage
When validation fails, the application should:
- stop the unsafe operation
- report a clear error
- close open resources safely
- preserve unrelated user data
- clean temporary state when safe
It must not delete unrelated files or damage the operating system.
Integrity and trust are different.
A package can pass its internal validation while still coming from an untrusted source.
Users should consider:
- where the package came from
- who created it
- expected package size
- published hashes when available
- package metadata
- whether the package is appropriate for the files being installed
Passing an integrity check is not proof that a package source is trustworthy.
Potential security problems should be reported according to REPORTING_GUIDELINES.md.