# Pitfall Log

Project: Unstructured-IO/unstructured

Summary: Found 22 structured pitfall item(s), including 3 high/blocking item(s). Top priority: Installation risk - Installation risk requires verification.

## 1. Installation risk - Installation risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/Unstructured-IO/unstructured/issues/3871

## 2. Installation risk - Installation risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/Unstructured-IO/unstructured/issues/4320

## 3. Security or permission risk - Security or permission risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: packet_text.keyword_scan | https://github.com/Unstructured-IO/unstructured

## 4. Installation risk - Installation risk requires verification

- Severity: medium
- Evidence strength: runtime_trace
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Repro command: `docker run -dt --name unstructured downloads.unstructured.io/unstructured-io/unstructured:latest # this will drop you into a bash shell where the Docker image`
- Evidence: identity.distribution | https://github.com/Unstructured-IO/unstructured

## 5. Capability evidence risk - Capability evidence risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: README/documentation is current enough for a first validation pass.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/Unstructured-IO/unstructured

## 6. Runtime risk - Runtime risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this runtime risk before relying on the project: Number getting converted into scientific notation in metadata.text_as_html
- User impact: Developers may hit a documented source-backed failure mode: Number getting converted into scientific notation in metadata.text_as_html
- Evidence: failure_mode_cluster:github_issue | https://github.com/Unstructured-IO/unstructured/issues/3871

## 7. Maintenance risk - Maintenance risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/Unstructured-IO/unstructured

## 8. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: no_demo
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/Unstructured-IO/unstructured

## 9. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: no_demo
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/Unstructured-IO/unstructured

## 10. Runtime risk - Runtime risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this performance risk before relying on the project: [Feature Request] Add document layout analysis confidence scores
- User impact: Developers may hit a documented source-backed failure mode: [Feature Request] Add document layout analysis confidence scores
- Evidence: failure_mode_cluster:github_issue | https://github.com/Unstructured-IO/unstructured/issues/4320

## 11. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: issue_or_pr_quality=unknown。
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/Unstructured-IO/unstructured

## 12. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: release_recency=unknown。
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/Unstructured-IO/unstructured

## 13. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.23
- User impact: Upgrade or migration may change expected behavior: 0.22.23
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.23

## 14. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.27
- User impact: Upgrade or migration may change expected behavior: 0.22.27
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.27

## 15. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.28
- User impact: Upgrade or migration may change expected behavior: 0.22.28
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.28

## 16. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.29
- User impact: Upgrade or migration may change expected behavior: 0.22.29
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.29

## 17. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.30
- User impact: Upgrade or migration may change expected behavior: 0.22.30
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.30

## 18. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.31
- User impact: Upgrade or migration may change expected behavior: 0.22.31
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.31

## 19. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.32
- User impact: Upgrade or migration may change expected behavior: 0.22.32
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.32

## 20. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.22.6
- User impact: Upgrade or migration may change expected behavior: 0.22.6
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.22.26

## 21. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.23.0
- User impact: Upgrade or migration may change expected behavior: 0.23.0
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.23.0

## 22. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: 0.23.1
- User impact: Upgrade or migration may change expected behavior: 0.23.1
- Evidence: failure_mode_cluster:github_release | https://github.com/Unstructured-IO/unstructured/releases/tag/0.23.1