junit-xml-2
Fork of https://github.com/kyrus/python-junit-xml that has tarball published to pypi
Decision gist · record as of 2026-08-14
Yes, if you need a stable, unchanging JUnit XML writer and are comfortable with an abandoned package. The low install friction, permissive license, and zero known vulnerabilities make it safe to use. However, only adopt it if you've confirmed that no actively maintained alternative meets your needs—abandonment means no bug fixes, security patches, or feature updates will arrive.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Low install friction with a single lightweight dependency (six).
- However, the package is abandoned—last release was 2020-09-30 and no commits or maintenance activity since.
- Use only if you need a stable, unchanging JUnit XML writer and cannot depend on actively maintained alternatives.
License · maintenance · safety
MIT (permissive) — MIT license permits unrestricted use, modification, and distribution with minimal restrictions, making it safe for commercial and open-source projects.
last release 2020-09-30 (2144 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 205,805 downloads/mo, #9,581 on PyPI
Alternatives
Verify before relying
pip install junit-xml-2
from junit_xml import TestCase, TestSuite
test_case = TestCase('test_name')
test_suite = TestSuite('suite_name', [test_case])
with open('output.xml', 'w') as f:
TestSuite.to_file(f, [test_suite])- Whether the fork diverges meaningfully from the original kyrus/python-junit-xml or serves only as a PyPI distribution vehicle
- Current compatibility with modern Python versions beyond what classifiers indicate
- Whether active maintenance has resumed or if this remains a static snapshot
What it is and what it does
junit-xml-2 is a fork of the original python-junit-xml library, packaged for PyPI distribution. It generates JUnit XML test result files from Python test data—a format widely supported by CI/CD platforms, test aggregators, and IDE test runners. The package takes test case and suite objects and serializes them to XML that conforms to the JUnit schema, allowing test results to be reported and tracked across build pipelines.
The package depends only on six for Python 2/3 compatibility, keeping installation lightweight. However, it is abandoned: the last release was September 2020 with no subsequent maintenance. It exists primarily to serve as a stable, published distribution for projects like Homebrew that need a PyPI-hosted version. If you need active development, bug fixes, or support for evolving test standards, you should evaluate maintained alternatives.
Use it for
- Export test results from a Python test runner to JUnit XML for ingestion by Jenkins, GitLab CI, or GitHub Actions
- Generate test reports that can be parsed and aggregated by test management or quality dashboard tools
- Integrate custom Python test frameworks with CI/CD systems that expect JUnit-formatted output
- Create test result artifacts for Homebrew or other package managers that depend on PyPI-hosted JUnit XML generation
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need a stable, unchanging JUnit XML writer and are comfortable with an abandoned package.
The low install friction, permissive license, and zero known vulnerabilities make it safe to use. However, only adopt it if you've confirmed that no actively maintained alternative meets your needs—abandonment means no bug fixes, security patches, or feature updates will arrive.
Install
junit-xml-2 on PyPI
Before you install
Low install friction with a single lightweight dependency (six). However, the package is abandoned—last release was 2020-09-30 and no commits or maintenance activity since. Use only if you need a stable, unchanging JUnit XML writer and cannot depend on actively maintained alternatives.
License in practice
MIT license permits unrestricted use, modification, and distribution with minimal restrictions, making it safe for commercial and open-source projects.
Quickstart
pip install junit-xml-2
from junit_xml import TestCase, TestSuite
test_case = TestCase('test_name')
test_suite = TestSuite('suite_name', [test_case])
with open('output.xml', 'w') as f:
TestSuite.to_file(f, [test_suite])Verify before relying
- Whether the fork diverges meaningfully from the original kyrus/python-junit-xml or serves only as a PyPI distribution vehicle
- Current compatibility with modern Python versions beyond what classifiers indicate
- Whether active maintenance has resumed or if this remains a static snapshot
Package facts
| License | MIT permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagesix |
| Maintenance | Abandoned 2,144 days since the last release |
| First released | |
| Downloads | 205,805 / month, #9,581 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableIntended Audience :: DevelopersLicense :: Freely DistributableLicense :: OSI Approved :: MIT LicenseOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 3Topic :: Software Development :: Build ToolsTopic :: Software Development :: Testing |
Evidence: junit_xml_2-1.9-py2.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 › “junit xml test reporting”
- junit-xml-2Generates JUnit XML test result reports from Python test data,…
- flake8-junit-report-basicConverts flake8 linting output to JUnit XML format for display in CI…
- flake8-formatter-junit-xmlFormats flake8 linting output as JUnit XML, enabling integration with…
Give your agent the search over MCP, or paste the wish link into any chat.
More Testing packages
Pluggy provides a plugin system that lets you define hook specifications and register implementations to be called in sequence, enabling extensible Python applications without tight coupling.
Install it if you're building an extensible application or framework.
pytest is a testing framework that lets you write test functions using plain assert statements and automatically discovers and runs them, with detailed failure reporting.
virtualenv creates isolated Python environments where packages can be installed independently without affecting the system Python or other projects.
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
pytest-asyncio is a pytest plugin that enables writing and running async test functions using the asyncio library, allowing developers to await code directly within test cases.
Install it if you write tests for any asyncio-based code.
A pytest plugin that generates test reports in Common Test Report Format (CTRF) as JSON, compatible with pytest-xdist and pytest-playwright for distributed and browser-based testing.
Install it if you need CTRF-formatted test output for CI/CD integration or cross-tool reporting.
See also flake8-formatter-junit-xml · junit-xml · pylint-junit · junit2html · xmlrunner · unittest-xml-reporting · secscanner2junit · flake8-junit-report · junitparser · flake8-junit-report-basic