martinlindhe/data-currencies

Release historydanger

The package has had only two releases, both in August 2015, with no releases in the last 12 months. For a currency-data package, such a long release gap creates a meaningful staleness risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository having stopped changing about 11 years ago. This materially increases abandonment and stale-data risk.

Repo toolingcaution

Composer is used for builds, which fits the package ecosystem, but no security-scanning tooling is present. That is a minor transparency gap, outweighed by the much older maintenance concern.

Security policycaution

The repository has no security policy. For a small static data package this is a minor transparency gap, but it offers no documented process for reporting issues.

Version stabilitycaution

Version 0.1.2 is not a prerelease, which avoids prerelease instability, but the package has remained below 1.0 throughout its entire roughly 11-year lifetime.