Skip to content

v0.1.0-alpha.0

Pre-release
Pre-release

Choose a tag to compare

@KROFN KROFN released this 15 Jun 23:54

PackGuard v0.1.0-alpha.0

First alpha release of PackGuard: a safety-first, manifest-based sync toolkit for Minecraft modpack maintainers.

This is an alpha release. PackGuard is not production-ready yet.

What is included

This alpha includes the first complete CLI/core workflow:

  • manifest v1 validation
  • source policy checks
  • target path safety checks
  • read-only target scanning for mods/**/*.jar
  • dry-run planning
  • guarded apply with --yes
  • verified cache usage
  • backup-before-replace
  • transaction journals
  • guarded rollback with --yes
  • rollback safety backups
  • status and doctor commands
  • transaction, rollback, and backup inspection
  • JSON output for supported commands
  • local fake end-to-end tester kit
  • release gate with typecheck, tests, CLI smoke, E2E tester kit, docs link check, and no-real-mod fixture verification

Quickstart from source

pnpm install
pnpm run release:check

Run the local fake E2E tester kit:

pnpm run example:e2e:run

Run the built CLI:

pnpm run cli:build
node packages/cli/dist/index.js --help

CLI package artifact

This release attaches the packed CLI artifact:

packguard-cli-0.1.0-alpha.0.tgz

The package contains the built CLI entrypoint and package metadata. It is intended for early local inspection/testing, not production deployment.

Safety notes

PackGuard verifies file integrity relative to a manifest and records auditable local sync transactions.

PackGuard does not:

  • make mods safe
  • prove mods are legal to redistribute
  • scan for malware
  • replace Modrinth, CurseForge, or any mod registry
  • act as a Minecraft launcher
  • provide a production-ready desktop workflow

Known limitations

  • This is not production-ready.
  • Desktop reattachment to the core engine is not implemented.
  • Backup-id rollback is not implemented.
  • Cache maintenance commands are not implemented.
  • Extra files are skipped by default; moving/disabling extras is not implemented.
  • Apply support is intentionally limited to mods/*.jar.
  • Config, resource pack, shader pack, and arbitrary file sync are not implemented.
  • Symlink hardening remains future work.
  • Provider integrations and automatic latest-version behavior are not implemented.
  • The CLI currently focuses on local manifest workflows.

Testing

Before this release, the local release gate passed:

pnpm run release:check

The gate includes:

  • TypeScript typecheck
  • core tests
  • CLI tests
  • preserved desktop fixture tests
  • built CLI smoke checks
  • fake E2E apply/rollback tester kit
  • local Markdown link check
  • no-real-mod fixture verification
  • CLI package packing

Reporting issues

Please use GitHub Issues for alpha feedback.

Do not attach real Minecraft mod .jar files, private manifests, secrets, or personal machine paths. If a report could expose a filesystem safety or security-sensitive issue, follow SECURITY.md instead of posting exploit details publicly.