daltonmccleery/remote-models

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository having received no push for over 18 months. This materially raises abandonment risk.

Release historycaution

The package has 18 releases but none in the last 12 months, and its latest release was over 18 months ago. This is meaningful maintenance risk despite the earlier release history.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a real transparency gap for a package handling remote application data.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous sinks or audit findings, but both of its two action references are unpinned. That weakens build reproducibility and update safety without showing an active exploit path.