Redaxa: baixar versions anteriors

Routine maintenance update.

Routine maintenance update.

Redaxa 0.6.7 is a routine maintenance update that also makes the free trial read the same on every screen.
- The account dialog and some plan messages now describe the 3-day free trial like the rest of Redaxa, in English, Italian, Spanish, French and German.
- Current Tauri window and webview components and an updated set of trusted root certificates.

Redaxa 0.6.6 keeps the free trial button in the sidebar tidy in every language and shows it on narrow windows too.
- The arrow of "Start your 3-day free trial" no longer drops onto a line of its own, in English, Italian, Spanish, French and German.
- On phones and very narrow windows the free trial offer stays in the top strip.

Redaxa 0.6.5 makes the 3-day free trial easy to find and fixes the plan labels on Plans & pricing.
- Plans & pricing and the sidebar offer "Start your 3-day free trial" to accounts that can still start one, show "Trial — X days left" while it runs, and say plainly when it has been used.
- Every plan below the one you hold reads "Included in your plan".

Redaxa 0.6.4 is a routine maintenance update.

- Closing the window keeps Redaxa in the notification area. Click its icon to reopen it, or right-click it for Open Redaxa and Exit Redaxa.
- Turn off Keep running in the background from the icon's menu if you prefer closing the window to quit. Your choice is saved.
- Opening Redaxa, or a redaxa:// link, while it is already running brings its window back. Reopening it also checks for updates.

Redaxa 0.6.2 checks files with long runs of spaces or tabs in a fraction of a second, and can receive updates from our own download server, dl.pctweaker.app, as well as from GitHub.
- Faster checks on unusual files: a file or prompt with a very long run of spaces or tabs could hold a check for several seconds. It now takes milliseconds, and settings with long names, such as PRODUCTION_DATABASE_PASSWORD=..., are still found.
- Updates from dl.pctweaker.app: when Redaxa checks for a new version, it asks dl.pctweaker.app first. If that server has nothing to offer, it asks GitHub, as before.
- An update is installed only when it carries Redaxa's update signature and its signed file name and version match the release on offer. Redaxa accepts it only from the Redaxa release folder on dl.pctweaker.app or the Redaxa release on GitHub.
- Version 0.6.1 was prepared but never published. Its changes are part of this release.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.6.0 installs for everyone on the computer, in Program Files\Redaxa as Redaxa.exe, and setup now ends by offering to start Redaxa and to put a shortcut on the desktop. Updating moves your current installation there by itself; settings, history and sign-in stay as they are.
- Setup installs Redaxa for all users in C:\Program Files\Redaxa, and the program is Redaxa.exe. Windows asks for administrator permission when you install or update.
- The last page of setup offers "Run Redaxa" and "Create desktop shortcut", both ticked. The Start menu entry is created as before, and uninstalling removes the program, the Start menu entry and the desktop shortcut; your settings stay unless you choose to delete the app data.
- Updating from 0.5.5 or earlier moves the installation from your user folder (%LocalAppData%\Redaxa) to Program Files: the old copy, its entry in Installed apps and its Start menu shortcut are removed, and a desktop shortcut or taskbar pin you had opens the new program. Settings, check history and the saved sign-in are kept, because they are stored apart from the program.
- Plans & pricing reads its prices from the payment provider, and your account shows when a payment did not go through, with a button to update the payment method.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.5.5 brings the newer detection to the Windows app's local repository check: secrets assigned by name in .env and configuration files, passwords inside connection URLs and three more provider keys, with fewer false alarms in code. It also keeps you signed in when the computer's clock is wrong.
- Secrets assigned by name in .env files and configuration (DB_PASSWORD=…, JWT_SECRET: …, "apiKey": "…") are found and shown as "Secret in a configuration value". Only literal values with letters and digits count; type names, environment references and code expressions are left alone.
- Passwords inside connection URLs such as postgres://app:…@db.internal/main are found and shown as "Password in a URL". Only the password is masked, so the scheme, user and host stay readable. Neither kind is tested for validity, so the repository check lists them for review at high priority, or medium in example files.
- Stripe webhook signing secrets, SendGrid API keys and Slack incoming webhook URLs are recognised with their service. AWS secret access keys are also found under the names the AWS CLI and SDKs print (SecretAccessKey, secretAccessKey, aws_secret_key).
- "The password is …" is caught as well as "password: …", and an IBAN followed by its BIC or another word in capitals is no longer missed.
- Fewer false alarms: password: string, process.env.API_KEY, git@github.com remotes and 13-digit millisecond timestamps that happen to pass the card checksum are no longer reported. A password-like value in a code comment is described as "Usually a placeholder".
- Sign-in: when the Redaxa service refuses a session this computer's clock still considers valid (a clock set back after sign-in, or a session ended elsewhere), the app asks the service once for a refreshed session instead of signing you out.
- Text fields show a single focus ring instead of two concentric lines.
- Detection relies on patterns and checksums, so it can miss sensitive information; review results before relying on them.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.5.4 finds AWS secret access keys and UK National Insurance numbers, and no longer counts a mistyped Italian fiscal code as one.
- AWS secret access keys are found next to an aws_secret_access_key or secret_access_key assignment, in prompt checks and in the repository check. A bare 40-character string is not flagged, and AWS's documented example key and filler values are ignored. The key is not tested against AWS, so the repository check lists it for review at high priority.
- UK National Insurance numbers are found with or without spaces and shown as "NI number". Prefixes that are never issued, such as QQ and BG, and placeholder digits like 123456 are ignored.
- An Italian fiscal code now needs a correct check letter, so a mistyped or invented code is no longer reported.
- The Redaxa service lets browsers reuse its CORS preflight answer for ten minutes, so the website and the browser extension repeat fewer OPTIONS requests.
- Detection relies on patterns and checksums, so it can miss sensitive information; review results before relying on them.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.5.3 stops listing test and example values, such as a webhook secret written for a test, as exposures in the repository check.
- Values in test, fixture, mock, sample and example folders or in test-named files, and values marked as test or placeholder data, are counted on one line ("N test or example values not reported") and are no longer listed, in the app, in the web check and in the downloaded report. Their values are never shown.
- A value in a test file that looks like a real key, such as a live Stripe key, a real-format AWS or GitHub key, or a complete private key, is still listed at low priority and marked "found in a test file".
- If the same value also appears outside the test files, it is listed as before.
- On the light Paper palette, the priority counts and alerts in repository results now use darker colours that are easier to read.
- The separation relies on file paths and value patterns, so it can miss sensitive information; review a report before relying on it.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.5.2 closes itself before an update replaces its files, so updates no longer stop with "Error opening file for writing".
- Updating from the app, or running a downloaded installer while Redaxa is open, now closes Redaxa and its local repository scanner first, waits until their files are free, and reopens Redaxa when an update from the app finishes.
- Only Redaxa's own processes, started from its installation folder, are closed.
- If an earlier update stopped with that message, click Retry after a few seconds, or close Redaxa and run the latest installer from the website.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.5.1 starts everyone in the light Paper theme unless they picked another one, including people whose earlier version saved the old default for them.
- Paper is the starting theme everywhere: the app, the website, its guides and its policy pages.
- If an earlier version saved Petrol & Copper without you choosing it, Redaxa now opens in Paper. A theme you pick in Settings is remembered as your choice; if you had picked Petrol & Copper yourself, choose it once more there.
- Sign-in and account dialogs on the website follow the theme as well.
- The window opens in Paper, with no dark frame while the app loads.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.5.0 redesigns the app: one sidebar with a page for every task, a full Plans & pricing page, and a light Paper theme for anyone who has not chosen one.
- Check text, Repository check, Activity, Protected terms, Settings, Account & team and Plans & pricing each have their own page, reached from a sidebar that keeps your plan and account at the bottom.
- Check results are grouped by severity, from critical to low, and every value found is highlighted in your text.
- Plans & pricing is now a full page with your current plan, a side-by-side comparison, what leaves your device, and answers to common questions.
- Paper is the new default theme and Ink & Copper its dark counterpart. A theme you already picked stays as it is.
- Sign-in, account and team dialogs follow your theme, with readable fields in every palette.
- Pages switch as soon as you click, and the window opens at 1280 × 820.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.4.13 brings the Halloween offer to Plans & pricing: at least 50% off your first month or year of Pro or Business until 6 November.
- Plans & pricing shows the offer with a live countdown, the struck-through price and the price you pay at renewal, in all five interface languages.
- When the offer ends, regular prices come back on their own, even if the app stays open.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication.

Redaxa 0.4.12 makes repository checks much faster on large files and tightens account security.
- Repository checks finish quickly on files with thousands of matches, such as data exports and minified bundles. Line numbers and findings are unchanged, and when a report reaches its display limit, API keys and other credentials are listed before personal data.
- Some unusual text patterns no longer slow down a prompt check.
- Scan API keys now work only with the Scan API, as the API documentation describes.
- Signed-in web sessions accept requests only from Redaxa's own pages, and confirmation and reset emails only link back to Redaxa.
- The free daily allowance no longer stores network addresses. The privacy policy now describes automatic checks in the browser extension, the activity history kept for signed-in accounts, and every service involved.
- In audit exports, member addresses that a spreadsheet would treat as formulas open as plain text.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication. Repository matches remain review candidates; no detector can guarantee zero false positives or prove that a credential is active.

Redaxa 0.4.11 is a routine maintenance update.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication. Repository matches remain review candidates; no detector can guarantee zero false positives or prove that a credential is active.

Redaxa 0.4.10 cleans up after the PromptShield name.
- Installing or updating Redaxa removes a leftover "PromptShield" entry from Installed apps when the old PromptShield program is no longer on the computer. A PromptShield installation that still works is left as it is, and no app data is touched.
- The Windows download on the website starts the installer directly.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication. Repository matches remain review candidates; no detector can guarantee zero false positives or prove that a credential is active.

Redaxa 0.4.9 refreshes the Windows app and makes the window easier to handle.
- Drag the window from anywhere on the title bar, and double-click it to maximise or restore.
- Redaxa reopens where you left it, at the same size.
- A cleaner workspace: the prompt and its results share one panel, the sidebar keeps the same icons on every page, and dividers and numbers line up.
- Repository checks raise fewer false alarms on public projects: published demo keys, placeholders and test fixtures are reported as low.
- Accounts without a plan go straight to their 5 free daily checks instead of the sign-up dialog.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication. Repository matches remain review candidates; no detector can guarantee zero false positives or prove that a credential is active.

Redaxa 0.4.8 gives free accounts daily checks and recognises more kinds of tokens.
- Signed-in accounts without a plan get 5 free prompt checks a day, counted per account, before a plan is needed.
- Detects npm, PyPI, GitLab and Hugging Face access tokens.
- Pasting into the app works again where Windows clipboard access was blocked.
- Signing out on this PC no longer signs you out on your other devices.
- After checkout, the browser returns to redaxa.getcertsprint.com.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication. Repository matches remain review candidates; no detector can guarantee zero false positives or prove that a credential is active.

Redaxa 0.4.7 improves team access security, explicit account consent and scanning resilience.
- Removing an accepted teammate also removes their organization access. Invitation creation and acceptance enforce paid seat limits atomically.
- Team links show a verified invitation before joining; opening a link no longer silently joins a workspace.
- Account tokens in URL fragments cannot silently replace your signed-in identity. Password recovery still uses its explicit form.
- Private-key parsing handles large, malformed inputs without repeated expensive matching.
- Includes the latest website readability, branded email and canonical link improvements.
Windows installers require verified Aurelio Avila publisher signatures, trusted timestamps and compatible updater signatures before publication. Repository matches remain review candidates; no detector can guarantee zero false positives or prove that a credential is active.

Redaxa 0.4.6
A refined desktop workspace with clearer credential reviews and more consistent navigation.
- New workspace typography, integrated window controls and improved layouts for prompt and repository checks.
- Updated theme selection, early theme restoration and account loading states that avoid briefly showing signed-out controls.
- Clearer redaction previews and controls to show individual findings, a section or all findings.
- More conservative credential classification: explicit placeholders and unsigned JWT examples are separated; unattributed strings show their uncertainty.
- Finding priority and API notifications share the same confidence rules. Reports include detection confidence and provider-specific response guidance where supported.
- Existing account, support and trial eligibility fixes are preserved.
Repository scans require Pro or Business. Matches are candidates for review, not proof that a credential works or belongs to a particular account. No discovered credential is tested against its provider.

# Redaxa 0.4.5

- Clearer credential review: probable service, key type, evidence and the recommended response now accompany prompt results on web and Windows, and in extension 0.4.3.
- Improved Bearer-token handling, stricter JWT structure and issuer checks, and detection of Supabase secret keys, Slack app tokens, Stripe restricted test keys and AWS temporary access-key identifiers.
- Public client keys and explicit placeholders stay separate from secret alerts. AWS identifiers and Google browser keys receive context-specific guidance; no claim of working credentials or verified ownership.
- Extension 0.4.3 adds manual text checks, redacted copy, Clear and an easier first-use path using the existing five-check daily anonymous allowance. Chrome Web Store approval is separate from this desktop release.

No discovered credential is tested against its provider. If a genuine secret has been exposed, removing it from the repository does not revoke it; follow the issuing service's rotation or invalidation process.

Detection references: [GitHub token types](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github), [Anthropic authentication](https://platform.claude.com/docs/en/manage-claude/authentication), [Stripe keys](https://docs.stripe.com/keys), [Supabase keys](https://supabase.com/docs/guides/getting-started/api-keys), [Slack tokens](https://docs.slack.dev/authentication/tokens/), [AWS access-key IDs](https://docs.aws.amazon.com/STS/latest/APIReference/API_GetAccessKeyInfo.html).

Redaxa 0.4.4
- A more consistent Ocean workspace, clearer typography and easier-to-read repository findings.
- Simpler Pro and Business pricing with a shared monthly/yearly selector.
- More reliable account sessions during token refresh and temporary service interruptions.
- Repository results retain distinct credentials when repeated matches reach the result limit.
- Updated product explanations and subscription guidance.
Repository checks identify possible exposures; they do not verify that credentials are valid. Review findings before taking action. The matching Chrome extension update also prevents an earlier scan from sending or overwriting a prompt edited afterwards; extension distribution follows the Chrome Web Store review process.