mitsuhiko/sloppy-xml-py
A Python library to parse malformed XML
- Repository: https://github.com/mitsuhiko/sloppy-xml-py
- Commit:
74a02907a402eed6d0016bfacca5db3d72003be5 - Generated: 2026-11-13T23:44:07+00:00
- Scorer 0.1.0, scoring prov-4+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | possible | 49% | 100% |
| Code quality | 71 | adequate | 90% | 100% |
| Security | 62 | weak | 85% | 100% |
AI provenance
Weak signals consistent with AI-assisted development.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
AI tooling configured in repo: claude-code
-
Stylometry index: 1.80 per 1,000 lines (narrated steps 1, placeholders 1, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2025-06 | 5,497 | 0% |
| 2026-01 | 129 | 0% |
Evidence
- CLAUDE.md (claude-code configuration) (CLAUDE.md)
- step-by-step narration comment: # First, find all entity positions to avoid escaping & characters within entities (sloppy_xml.p)
- placeholder or demo-only phrasing: # This is a simplified implementation - could be much more sophisticated (sloppy_xml.p)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is adequate: test-to-source ratio 0.97, CI runs tests; 59% of function code in complex or long functions; 7% duplicated lines. Weakest area: complexity.
| Area | Score |
|---|---|
| Complexity (lizard) | 17 |
| Duplication | 66 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 100 |
| Documentation | 85 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 37; mean complexity 5.6, 90th percentile 15; 3 complex and 1 long functions
- Duplicated lines: 7.0% of 1,304 compared
- Tests: 1,613 test lines for 1,662 source lines (ratio 0.97); CI test commands: pytest; 54% of recent source commits also change tests
- Docs missing or thin: contributing
Most complex functions:
- stream_parse in sloppy_xml.py: complexity 60, 352 lines
- stream_parse.flush_text in sloppy_xml.py: complexity 24, 87 lines
- _repair_attributes in sloppy_xml.py: complexity 19, 49 lines
Security
Security posture is weak: 2 high-severity SAST findings; 7 high-severity workflow issues. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 73 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | 26 |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] |
sloppy_xml.py:13 |
| high | opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] |
sloppy_xml.py:1194 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/release.yml:16 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/release.yml:19 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/release.yml:33 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/release.yml:36 |
| high | zizmor/cache-poisoning: runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] |
.github/workflows/release.yml:19 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/test.yml:17 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/test.yml:20 |
| medium | zizmor/artipacked: credential persistence through GitHub Actions artifacts [confidence low] |
.github/workflows/release.yml:16 |
| medium | zizmor/artipacked: credential persistence through GitHub Actions artifacts [confidence low] |
.github/workflows/test.yml:17 |
| medium | zizmor/excessive-permissions: overly broad permissions [confidence medium] |
.github/workflows/test.yml:10 |
| info | zizmor/superfluous-actions: action functionality is already included by the runner [confidence high] |
.github/workflows/release.yml:36 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Distribution signals
- binary-release-asset: release 0.3.1 ships sloppy_xml-0.3.1.tar.gz (2 downloads)
- binary-release-asset: release 0.3.0 ships sloppy_xml-0.3.0.tar.gz (2 downloads)
- binary-release-asset: release 0.2.1 ships sloppy_xml-0.2.1.tar.gz (6 downloads)
- binary-release-asset: release 0.2.0 ships sloppy_xml-0.2.0.tar.gz (3 downloads)
- binary-release-asset: release 0.1.0 ships sloppy_xml-0.1.0.tar.gz (2 downloads)
Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.
Repository profile
- Source lines: 1,662; test lines: 1,613
| Language | Lines |
|---|---|
| Python | 3,275 |