scitex-dev
Shared developer utilities for the SciTeX ecosystem
Decision gist · record as of 2026-08-14
Yes, if you maintain or develop within the SciTeX ecosystem—it directly solves the coordination and consistency problems described in its problem table. No, if you are outside that ecosystem: the audit rules, skills system, and ecosystem commands are tightly coupled to SciTeX conventions and will not transfer. The AGPL-3.0 license also requires your project to be open-source under compatible terms or kept private.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9+.
- Designed for use within the SciTeX ecosystem; utility outside that context depends on whether your project structure matches SciTeX conventions.
- Low install friction: pure Python wheel with 15 runtime dependencies including click, pyyaml, textual, and rich.
License · maintenance · safety
AGPL-3.0-only (agpl) — AGPL-3.0-only: using this package in your own project requires you to license that project under AGPL-3.0 or compatible terms, or keep it private. Suitable for internal tooling and open-source projects already under copyleft licenses.
last release 2026-08-13 (1 days) · last repo commit 2026-08-13
0 known vulnerabilities (OSV.dev, 2026-08-14) · 85,012 downloads/mo, #13,959 on PyPI
Alternatives
Verify before relying
pip install scitex-dev
scitex-dev ecosystem list
scitex-dev ecosystem audit-all
from scitex_dev import detect_mismatches, verify_versions
mismatches = detect_mismatches()
verify_versions()- Whether the ~130 audit rules are documented and discoverable outside the source code.
- How the linter plugin system (scitex_dev.linter.plugins entry point) is extended by other packages.
- Whether skills exported to ~/.claude/skills/scitex/ work with Claude Desktop or other MCP clients without additional setup.
What it is and what it does
scitex-dev is a CLI and Python library that centralizes developer operations for a large ecosystem of related packages. It solves the coordination problem of keeping ~70 packages in sync: enforcing naming conventions, API rules, and project structure through an audit system with ~130 numbered rules; aggregating skills (workflow guides) from all packages for AI agent discovery; detecting and fixing version mismatches across the ecosystem; and performing bulk renames with cross-reference updates and safety checks. The package ships as a single install with no feature menu—everything (CLI, MCP server, icon rendering, skills) is included.
It provides four interfaces: a CLI (primary), a Python API for version management and CI/CD checks, an MCP server for integration with Claude, and a skills system that exports workflow guides to ~/.claude/skills/scitex/. The linter engine aggregates per-package rule plugins, allowing rules to ship alongside the code they enforce. Configuration lives in optional local-state directories (~/.scitex/dev/ and <proj-root>/.scitex/dev/) and can be overridden by environment variables or CLI flags.
Use it for
- Run ecosystem-wide audits to catch version drift, README inconsistencies, and API violations across 70+ packages in one command.
- Aggregate and export skills from all SciTeX packages so AI agents can discover and use them without manual curation.
- Detect and fix version mismatches across the ecosystem, then sync changes to all hosts in a single operation.
- Perform atomic bulk renames across multiple repos with automatic cross-reference updates and dry-run preview.
- Enforce linting rules tied to specific APIs, ensuring that renamed functions and their corresponding lint rules stay in sync.
- Query documentation and search across all ecosystem packages from the CLI or Python API.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you maintain or develop within the SciTeX ecosystem—it directly solves the coordination and consistency problems described in its problem table.
No, if you are outside that ecosystem: the audit rules, skills system, and ecosystem commands are tightly coupled to SciTeX conventions and will not transfer. The AGPL-3.0 license also requires your project to be open-source under compatible terms or kept private.
Install
scitex-dev on PyPI
Before you install
Low install friction: pure Python wheel with 15 runtime dependencies including click, pyyaml, textual, and rich. Active maintenance with a release 1 day old. Requires Python 3.9+.
Requires Python 3.9+. Designed for use within the SciTeX ecosystem; utility outside that context depends on whether your project structure matches SciTeX conventions.
License in practice
AGPL-3.0-only: using this package in your own project requires you to license that project under AGPL-3.0 or compatible terms, or keep it private. Suitable for internal tooling and open-source projects already under copyleft licenses.
Quickstart
pip install scitex-dev
scitex-dev ecosystem list
scitex-dev ecosystem audit-all
from scitex_dev import detect_mismatches, verify_versions
mismatches = detect_mismatches()
verify_versions()Verify before relying
- Whether the ~130 audit rules are documented and discoverable outside the source code.
- How the linter plugin system (scitex_dev.linter.plugins entry point) is extended by other packages.
- Whether skills exported to ~/.claude/skills/scitex/ work with Claude Desktop or other MCP clients without additional setup.
Package facts
| License | AGPL-3.0-only agpl |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 15 packagesscitex-configscitex-loggingclickpyyamltomlifastmcpnewbscitex-sshscitex-scholarPillowtomlkittextualpackagingrichpsycopg |
| Maintenance | Actively maintained 1 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 85,012 / month, #13,959 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: scitex_dev-0.49.3-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “ecosystem package auditing”
- scitex-devProvides unified developer tooling for the SciTeX ecosystem: audits…
- mythrilMythril analyzes EVM bytecode for security vulnerabilities in smart…
- pycadfPyCADF implements the Cloud Auditing Data Federation specification to…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also metagit-cli · apm-cli · plugin-scanner · pydantic-ai-skills · boost-skill-cli · skillsaw · agent_governance_toolkit · tooluniverse · skills-ref · ovos-utils