Differences

Differences from Bincache & SoarPkgs

PkgCache	BinCache	SoarPkgs
PreBuilt Package Cache, Only Packages from https://docs.pkgforge.dev/formats/packages	PreBuilt Binary Cache, Only Packages from https://docs.pkgforge.dev/formats/binaries	No PreBuilt Cache, All Packages are Built & Installed Locally
Targeted towards full-blown GUI Apps	Targeted towards CLI Apps	Targets both CLI/GUI Apps
Runs on Secure Isolated Containers & Transparent Build Logs are provided, but Security still depends on each Package	Runs on Secure Isolated Containers & Transparent Build Logs are provided, but Security still depends on each Package	.SBUILD runs Locally on User's System, so Security depends on each package & their Maintainers
Only Truly Portable Packages are accepted, i.e. all packages added must run on GLIBC/MUSL & Require no additional dependencies	Only Truly Portable Packages are accepted, i.e. all packages added must run on GLIBC/MUSL & Require no additional dependencies	No Restrictions of Addition/Acceptance of Packages
Centralized & Managed by PkgForge's Core Team	Centralized & Managed by PkgForge's Core Team	Decentralized
Only Storage (Disk) & Bandwidth is Used	Only Storage (Disk) & Bandwidth is Used	Local Resources like CPU, MEM, DISK, Bandwidth etc Are Used
Each Contribution goes through Rigorous Review before being Merged	Each Contribution goes through Rigorous Review before being Merged	Contribution GuideLine is Simple & Forgiving