Package pitty for Nix source builds

[kexi]

Why

pitty should be installable from source with Nix now, while keeping the package expression close to what nixpkgs expects for a future official package submission.

What

• add a nixpkgs-style rustPlatform.buildRustPackage expression in nix/package.nix
• expose packages.default, packages.pitty, apps.pitty, and checks.pitty from the flake
• track Cargo.lock so application source builds are reproducible
• document Nix install/build/run flows and nixpkgs submission notes

Verification

• nix build .#pitty
• ./result/bin/pitty --version
• nix run .#pitty -- --version
• nix flake check
• git diff --cached --check

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	serde@​1.0.228
	serde_json@​1.0.150
	clap@​4.6.1
	portable-pty@​0.8.1
	regex@​1.12.3
	serde_norway@​0.9.42
	tempfile@​3.27.0
	similar@​2.7.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo libc is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/tempfile@3.27.0 → cargo/portable-pty@0.8.1 → cargo/libc@0.2.186 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/libc@0.2.186. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report