License FAQ

What is postq.lic?

It is a signed offline entitlement envelope for PostQ Code Scanner. The scanner verifies it with a packaged public key. Editing any signed content invalidates the signature.

How long is the beta trial?

The V1 trial is issued for 15 days. It must also fall inside the beta availability window of 21 August 2026 through 30 September 2026 UTC. The earlier effective end controls.

What are the default trial limits?

The current default is 20 unique repositories and 1,000 eligible source files per repository. The signed claims in the issued license are authoritative.

Does activation require internet access?

No. Signature, date, product, limit, and usage-ledger checks are local. License validation does not send source, findings, repository identity, or usage data to PostQ.

Where should I store the license?

Use an approved secret/configuration directory readable only by the scan account. In CI, use a protected file secret. In containers, mount the file read-only at a secrets path. Never bake it into an image or commit it to a repository.

What does the local ledger contain?

It tracks hashed repository identity and latest observed time needed for offline limit and rollback checks. It does not place source, findings, customer identity, repository paths, signatures, or license content in scanner reports.

Can I delete or edit the ledger?

Do not delete, edit, copy backward, or reset it. Treat it as protected product state. Tampering or clock rollback can prevent scanning and may conflict with the applicable terms.

Can I use one license in CLI, VS Code, Eclipse, and containers?

All hosts delegate validation to scanner-service, but permitted users, machines, environments, and distribution are governed by the issued entitlement and applicable agreement. Technical compatibility does not grant additional rights.

Does the Report Viewer consume a license?

No. Viewing completed reports does not run the scanner license gate.

What happens after expiration?

New scans in an enforced build fail with exit code 3. Existing reports remain readable. Contact the approved PostQ commercial/support channel for any extension or replacement entitlement; do not change dates in the file.

Why do I see a clock rollback error?

The local system time is earlier than the ledger's last observed UTC time beyond the allowed tolerance. Correct the host clock and time synchronization. Do not roll back or replace the ledger.

What information is safe to include in a support request?

Include the stable error identifier, product version, operating system, current UTC time, selected license path with sensitive directories redacted, and --license-status output. Do not include the license envelope, signature, source code, or ledger unless an approved secure support process explicitly requests it.