kwaadpepper/chronopost-relay

Project backingcaution

The repository is owned by the matching individual publisher account rather than an organization, so the small maintainer footprint is meaningful rather than normal organization publishing hygiene.

Release historycaution

Only two releases exist over about 3 years 9 months, with no release in the last 12 months; this suggests a small, infrequently updated project, though generated clients may change only when the service schema changes.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last 3 months, which weakens evidence of ongoing maintenance; the package's generated, narrowly scoped nature partly explains why activity may be low.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap, not evidence of unsafe code.

Security policycaution

The repository has no security policy. For a generated SOAP client this is a minor disclosure-process gap rather than a severe dependency risk.