meita/zatca-engine

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months. Combined with the old last push, this is concrete evidence of stalled maintenance for a relatively new package.

Project backingcaution

The source repository is owned by a GitHub user rather than an organization, and the registry namespace is likewise individual. This indicates a narrow backing structure and limited visible organizational continuity.

Release historycaution

All 18 releases arrived within about two days, with a median interval of roughly 16 minutes, and no newer release was observed over the following months. This suggests an immature release burst followed by inactivity.

Repo toolingcaution

Composer is used for the build, but no security-scanning tool was detected. That weakens automated oversight, though it is a hygiene concern rather than proof of a defective release.

Security policycaution

The repository has no security policy. For an invoicing and signing engine, this reduces transparency about vulnerability reporting and response expectations.