Skip to content
Back to the index

rulestamp-pg14-upgrade-blocker-lint

PyPIInfrastructure

No liveness check has reached it yet; it is registered on PyPI and has been in the index since 10 Oct 2026. How this is checked

rulestamp-pg14-upgrade-blocker-lint is a command-line linter for PostgreSQL 14-to-17 upgrade preparation. It identifies SQL and configuration lines removed in PostgreSQL 15, 16, and 17, and provides a fix for each finding; it includes a bundled Node.js runtime.

Inferred · not functionally tested

PaidProprietary - see LICENSE.txtCLI
Visit PyPI
1alternative
6features
2026since

Overview

6 features

Purpose: Finding and fixing SQL and configuration incompatibilities before upgrading PostgreSQL 14 to newer versions.

Inferred · not functionally tested

Audience: PostgreSQL developers and database administrators

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: unknown

Recorded constraints: pricing: paid · license: Proprietary - see LICENSE.txt · platforms: CLI · deployment: cli

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org. These links do not verify the individual claims.

rulestamp-pg14-upgrade-blocker-lint is a Testing & QA project. Inferred · not functionally tested: It focuses on finding and fixing SQL and configuration incompatibilities before upgrading PostgreSQL 14 to newer versions. Inferred · not functionally tested: It is built as a B2B product for postgreSQL developers and database administrators. Basis unknown · not verified: rulestamp-pg14-upgrade-blocker-lint is paid. Basis unknown · not verified: rulestamp-pg14-upgrade-blocker-lint is available on the command line.

rulestamp-pg14-upgrade-blocker-lint first shipped in 2026. Inferred · not functionally tested: Key capabilities include SQL linting, config linting, and upgrade checks.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • SQL linting
  • Config linting
  • Upgrade checks
  • Fix suggestions
  • PostgreSQL 17 support
  • Bundled runtime

Topics: Inferred · not functionally tested

Tags
postgresql-upgradessql-lintingdatabase-migrationsaurora-rds

JSON profile · Text profile · Access guide

Built with & integrations

Runs on
CLI

Trust & compliance

License
Proprietary - see LICENSE.txt
Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 04:49 UTC
    rulestamp-pg14-upgrade-blocker-lint seen via PyPI Bulk Enumerator
    Source: PyPI Bulk Enumerator · Open

Frequently asked questions about rulestamp-pg14-upgrade-blocker-lint

What is rulestamp-pg14-upgrade-blocker-lint?
Inferred · not functionally tested: Rulestamp-pg14-upgrade-blocker-lint focuses on finding and fixing SQL and configuration incompatibilities before upgrading PostgreSQL 14 to newer versions. It is catalogued under Testing & QA on PulseGate.
Who is rulestamp-pg14-upgrade-blocker-lint for?
Inferred · not functionally tested: rulestamp-pg14-upgrade-blocker-lint is a B2B product built for postgreSQL developers and database administrators.
Does rulestamp-pg14-upgrade-blocker-lint have a free plan?
Basis unknown · not verified: No — rulestamp-pg14-upgrade-blocker-lint is paid.
What platforms does rulestamp-pg14-upgrade-blocker-lint run on?
Basis unknown · not verified: rulestamp-pg14-upgrade-blocker-lint runs on the command line.
Is rulestamp-pg14-upgrade-blocker-lint still active?
Unverified. rulestamp-pg14-upgrade-blocker-lint has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
When did rulestamp-pg14-upgrade-blocker-lint launch?
rulestamp-pg14-upgrade-blocker-lint first shipped in 2026.

Similar projects

Closest matches by what these projects do