← Back to home
Comparison · Infra & APIs

goodpractice vs Port

A side-by-side editorial comparison of goodpractice and Port — release velocity, themes, recent moves, and the top alternatives to consider.

goodpractice vs Port: at a glance

FeaturegoodpracticePort
SectorInfra & APIsInfra & APIs
Velocity score0.03.8
Sparks · 30d01
Top themescode-quality, static-analysis, r-package, ropensciagentic sdlc, internal developer portal, mcp, workflow automation
Last editorial update1h ago6d ago
WebsiteVisit →Visit →

What is goodpractice?

The R package-quality checker returns from CRAN limbo with checks you can select by category.

goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.

Read the full goodpractice trajectory →

What is Port?

Port AI graduated from answering questions about the catalog to changing it, with approval.

Port is an internal developer portal whose center of gravity has moved to Port AI. Over ten months it went from an open-beta chat assistant to an agent that plans and executes real platform changes — creating blueprints, upserting entities, triggering workflows — behind a plan the user approves first. The surrounding platform work is almost entirely extensibility: a public plugins repo, Custom Widgets, Workflows in open beta, and MCP connectors that pull external tools into the same chat.

Read the full Port trajectory →

goodpractice vs Port: editorial side-by-side

G
goodpractice
INFRA · APIS
0.0

The R package-quality checker returns from CRAN limbo with checks you can select by category.

◆ Current state

goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.

◆ Where it's heading

The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.

◆ Prediction

With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.

P
Port
INFRA · APIS
3.8

Port AI graduated from answering questions about the catalog to changing it, with approval.

◆ Current state

Port is an internal developer portal whose center of gravity has moved to Port AI. Over ten months it went from an open-beta chat assistant to an agent that plans and executes real platform changes — creating blueprints, upserting entities, triggering workflows — behind a plan the user approves first. The surrounding platform work is almost entirely extensibility: a public plugins repo, Custom Widgets, Workflows in open beta, and MCP connectors that pull external tools into the same chat.

◆ Where it's heading

The arc is assistant to gateway to executor. March made Port AI a front end for other vendors' tools via external MCP servers; June put a visual automation builder underneath it; July let the AI drive both, with Plan and Build modes and per-step traces. Each release widens what the agent may touch while keeping a human approval gate in front of it, and the extensibility work — plugins, widgets, bring-your-own LLM endpoint — exists so customers can extend the surface the agent operates on.

◆ Prediction

Expect the approval gate itself to become the product surface: policy governing which plans may execute unattended, tied to the Dynamic RBAC and permissions simulator already shipped. The step-by-step plans and per-step traces in the July release are the groundwork for granting scoped autonomy.

Alternatives to goodpractice and Port

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either goodpractice or Port.

See all goodpractice alternatives → · See all Port alternatives →

Recent activity from goodpractice and Port

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 7d agoPortPort AI Builder plans and executes catalog changes with approval
  2. 1mo agoPortWorkflows hits open beta; AI agents connect external MCP servers
  3. 2mo agoPortPublic plugins repo opens Port to community contributions
  4. 2mo agogoodpracticeChecks organized into 16 selectable groups with presets
  5. 3mo agoPortCustom Widgets run your own UI inside Port; BYO OpenAI endpoint
  6. 4mo agoPortMCP Connectors turn Port AI into a gateway for external tools
  7. 5mo agoPortRun Claude in your own Azure; RBAC gets a UI and simulator
  8. 2y agogoodpracticerOpenSci takes over maintenance, package restored to CRAN
  9. 4y agogoodpracticeConfigurable cyclomatic complexity limit and output length
  10. 5y agogoodpracticePackage logo added

Frequently asked questions

What is the difference between goodpractice and Port?

They serve adjacent needs but don't currently overlap on shipped themes. Port is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is goodpractice better than Port?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Port is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to goodpractice?

Top goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.

What are the best alternatives to Port?

Top Port alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Port alternatives" section above for the current picks, or visit /alternatives/port for the full list with editorial commentary on each.