Ext Wortfreunde

D 57 completed
Other
unknown / php · tiny
22
Files
1,088
LOC
0
Frameworks
7
Languages

Pipeline State

completed
Run ID
#1544389
Phase
done
Progress
0%
Started
2026-04-16 22:41:50
Finished
2026-04-16 22:41:50
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
25.36
Framework unique
Isolation
Last stage change
2026-05-10 03:34:46
Deduplication group #47261
Member of a group with 442 similar repo(s) — canonical #187747 view group →
All rows scored by the Repobility analyzer (https://repobility.com)

AI Prompt

Create a TYPO3 extension connector using PHP that receives blog posts from an external source, specifically from [wortfreunde.ch], via webhooks. The system needs to process incoming POST requests at a defined webhook endpoint. It must verify the request signature using an HMAC-SHA256 secret and filter events based on allowed channel IDs. When processing events like `post.published`, it should create or update a `tt_content` element on a configured target page, mapping fields like the post title to `header` and the body to `bodytext` (after converting Markdown to HTML). The configuration should allow setting the webhook secret, allowed channels, and default content type.
php typo3 webhook extension rest-api content-management php-8.3 composer markdown
Generated by gemma4:latest

Catalog Information

Create a TYPO3 extension connector using PHP that receives blog posts from an external source, specifically from [wortfreunde.ch], via webhooks. The system needs to process incoming POST requests at a defined webhook endpoint. It must verify the request signature using an HMAC-SHA256 secret and filter events based on allowed channel IDs. When processing events like post.published, it should create or update a tt_content element on a configured target page, mapping fields like the post title

Tags

php typo3 webhook extension rest-api content-management php-8.3 composer markdown

Quality Score

D
56.9/100
Structure
38
Code Quality
75
Documentation
59
Testing
0
Practices
78
Security
100
Dependencies
80

Strengths

  • Good security practices — no major issues detected

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • No tests found — high risk of regressions
  • No CI/CD configuration — manual testing and deployment
  • 140 duplicate lines detected — consider DRY refactoring

Recommendations

  • Add a test suite — start with critical path integration tests
  • Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
  • Add a linter configuration to enforce code style consistency
  • Add a LICENSE file (MIT recommended for open source)

Languages

php
63.5%
html
20.8%
markdown
8.5%
json
3.3%
sql
1.8%
yaml
1.4%
text
0.6%

Frameworks

None detected

Symbols

method37
class5
constant1

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/1368103.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV