JustHandled Labs
// Productivity

Filename Portability Preflight

Flag reserved names, invalid characters, trailing dots, case collisions, Unicode normalization collisions, and path-length risks.

What problem does Filename Portability Preflight solve?

A folder that works on one operating system can fail to sync, unzip, or clone elsewhere because its names collide or violate another platform's rules.

Use it to

What it returns

A representative input and result

fixture-backed sample
input {"paths":["assets/logo.svg","docs/Guide.pdf"],"max_path_length":240}
result READY; two paths checked across reserved-name, character, case, Unicode, and length rules.

Access and approval boundaries

Known limitations

Questions

Does it change or upload anything?

No. It reads supplied local evidence and writes only to the selected output directory.

Is this an AI judgment?

No. The packaged checker is deterministic and applies documented rules to the supplied input.

What does a ready result mean?

It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.

How does malformed input behave?

Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.

Can I audit the result?

Yes. Every finding carries a stable code, record identifier, severity, source, and message.

Filename Portability Preflight keeps proof and approval boundaries visible.

The listing includes the tested package, realistic samples, declared permissions, and known limitations.

Get Filename Portability Preflight on Agensi