Adoption Check
Intended use: Example: currency-aware amounts in reconciliation scripts
Last checked 19 Oct 2026, 05:17 UTC · method 2026-10-12.2
85% of weight had data (partial)
py-moneyed/py-moneyed is evaluated as Risky due to a lack of active maintenance, showing no release and no default-branch commit in the last 365 days. Its OpenSSF Scorecard score is low at 3.2 out of 10, and no security policy (SECURITY.md) was found. The project also shows long-term stagnation, with the last release occurring 1,421 days ago (v3.0).
Licensed under BSD-3-Clause (OSI-approved).
Source: Licensed under BSD-3-Clause (OSI-approved).
368,774 downloads last week on PyPI.
Source: 368,774 downloads last week on PyPI.
No release and no default-branch commit in the last 365 days.
Source: No release and no default-branch commit in the last 365 days.
OpenSSF Scorecard score is 3.2 out of 10.
Source: OpenSSF Scorecard score is 3.2 out of 10.
Last commit to the default branch was 908 days ago.
Source: Last commit to the default branch was 908 days ago.
Uncertainty: Data is missing regarding CI status, median days between releases, issue and pull request responsiveness metrics, and package dependents.
Written by Gemini Flash from the metrics and reasons below; every number was checked against the data, and the verdict and score come from fixed rules, not the model.
Explained
7 concerns5 neutral2 positive
Score 41 from 85% of the weight; 1 hard gate applied.Breakdown
Weight 20
32Risky
Weight 15
100Healthy
no records in OSV
Weight 15
5Risky
Weight 10
10Risky
Weight 10
—No data
Insufficient data: Only 0 recent issues or PRs to sample
Weight 10
20Risky
Partial data: contributor count only
Weight 10
60Watch
Weight 5
—No data
Insufficient data: No checks or statuses on the default branch head
Weight 5
76Healthy
Over time
History
No decision recorded yet. Status: Evaluating.