Legacy Limits

Recent Obscura Flow versions use a dedicated Archive Package with the compressed archive, manifest.json, and signature.ed25519. Older formats remain visible when possible, but they do not provide the same guarantees.

Single-file archives

An archive created as a single file is displayed with a legacy status. If an adjacent manifest still exists, the application can use it to document the archive. Without manifest or signature, Obscura Flow cannot guarantee the full inventory or cryptographic identity of the package.

Restore from unsigned archive

An unsigned archive can be inspected or kept for migration, but it should not be treated as equivalent to a signed package. The recommended workflow is to rebuild an archive from the source project, then restore from the complete validated package.

Remote provider without checksum

Some remote providers do not return a usable checksum or use provider-specific checksums. In that case, Obscura Flow compares available sizes and metadata, then reports validation with the real level of assurance available. For byte-for-byte proof, download the remote package and run local validation again.