PerfectlySoft/Perfect

Introduced new \Bytes\, \Dir\, \File\, \JSONConvertible\, \Log\, \PerfectError\, \PerfectServer\, \SysProcess\, and \Utilities\ modules within \Sources/PerfectLib\. These additions provide foundational capabilities for handling byte arrays, managing the file system (including directory enumeration and path resolution), serializing objects to JSON, structured logging, and spawning external processes with standard I/O stream access.

Sources · high confidence

The repository now includes a Code of Conduct (in English and Simplified Chinese) and a Chinese translation of the main README. Additionally, a .gitattributes file was added to configure Linguist's file detection for vendored sources, and the .gitignore was updated to exclude Swift Package Manager build artifacts and Xcode project files.

(repo-wide) · high confidence

Added Linux test runner; Added initial test suite for PerfectLib.

A new Package.swift file has been added to the project, enabling Swift Package Manager (SPM) support. The configuration defines the 'PerfectLib' library and its test target. For Linux builds, it explicitly depends on the 'LinuxBridge' package (version 3.0.0), while macOS builds target OS X 10.15 and have no external dependencies. This change facilitates cross-platform compilation and dependency management via SPM.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 47 → 50 (+3.0)
• Rubric changed (rubric-2026.08.15 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 93 (-6.6)
• Architecture 94 (new)
• Maturity 55 → 34 (-21.3)
• Readiness 17 → 33 (+16.6)
• Security 100 → 95 (-5.0)

• Dimension evaluation failed
• No automated tests
• No exposed public API
• No tests found
• Test reliability not included
• The Getting Started link points to guide/gettingStarted.md rather than the README itself (the single README), which is nonstandard and makes it harder to find the main docs from the README. (README.md)

• Change coupling: Dir.swift ↔ Utilities.swift (Sources/PerfectLib/Dir.swift)
• Coverage not measured — Swift suite
• Dependency hygiene PARTLY measured — SwiftPM pinning read, dependency currency NOT established
• Dir.forEachEntry (cognitive 20) (Sources/PerfectLib/Dir.swift)
• Documentation: no installation or build instructions (README.md)
• Documentation: no project overview (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (17–21 lines × 3) (Sources/PerfectLib/JSONConvertible.swift)
• Further orphaned files (smaller)
• Inconsistent boolean parameter naming and usage. The concrete loggers (ConsoleLogger, SysLogger) use an unnamed Bool parameter, whereas the Log facade uses a named evenIdents: Bool. This makes the API confusing to use and suggests the boolean parameter's purpose is not clearly communicated or consistently applied.
• Inconsistent parameter signatures for log levels. The debug method uses an autoclosure for lazy evaluation, while all other methods (info, warning, error, critical, terminal) take a strict String and an additional evenIdents: Bool parameter. This breaks the uniform interface expected for a logging facade.
• JSONDecodeState.readNumber (cognitive 24) (Sources/PerfectLib/JSONConvertible.swift)
• JSONDecodeState.readNumber (cyclomatic 18) (Sources/PerfectLib/JSONConvertible.swift)
• JSONDecodeState.readObject (cognitive 72) (Sources/PerfectLib/JSONConvertible.swift)
• JSONDecodeState.readObject (cyclomatic 32) (Sources/PerfectLib/JSONConvertible.swift)
• JSONDecodeState.readString (cognitive 63) (Sources/PerfectLib/JSONConvertible.swift)
• JSONDecodeState.readString (cyclomatic 24) (Sources/PerfectLib/JSONConvertible.swift)
• Low cohesion: String (LCOM4 9) (Sources/PerfectLib/JSONConvertible.swift)
• MethodTooLong: String.stringByReplacing (Sources/PerfectLib/JSONConvertible.swift)
• Orphaned knowledge (Sources/PerfectLib/JSONConvertible.swift)
• …and 1 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

PerfectlySoft/Perfect was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.