Problem: the Scamalytics IP enricher used datetime.utcnow() when setting RiskProfile.last_updated. That helper is deprecated and returns a naive UTC timestamp.
Before / after: before, fraud score updates stored a naive UTC ISO string. After, the timestamp is produced with datetime.datetime.now(datetime.timezone.utc).isoformat(), preserving UTC while including explicit timezone information.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/reconurge/flowsint/pull/191
**Author:** [@Ghraven](https://github.com/Ghraven)
**Created:** 6/21/2026
**Status:** ✅ Merged
**Merged:** 7/1/2026
**Merged by:** [@dextmorgn](https://github.com/dextmorgn)
**Base:** `main` ← **Head:** `fix/fraudscore-aware-utc`
---
### 📝 Commits (1)
- [`0485fc1`](https://github.com/reconurge/flowsint/commit/0485fc17467ffb06e5c2aee67e79f6762cc97dfe) fix: use aware timestamp for fraud score updates
### 📊 Changes
**1 file changed** (+7 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `flowsint-enrichers/src/flowsint_enrichers/ip/to_fraudscore.py` (+7 -1)
</details>
### 📄 Description
Problem: the Scamalytics IP enricher used datetime.utcnow() when setting RiskProfile.last_updated. That helper is deprecated and returns a naive UTC timestamp.
Before / after: before, fraud score updates stored a naive UTC ISO string. After, the timestamp is produced with datetime.datetime.now(datetime.timezone.utc).isoformat(), preserving UTC while including explicit timezone information.
Verification: python -m py_compile flowsint-enrichers\src\flowsint_enrichers\ip\to_fraudscore.py
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/reconurge/flowsint/pull/191
Author: @Ghraven
Created: 6/21/2026
Status: ✅ Merged
Merged: 7/1/2026
Merged by: @dextmorgn
Base:
main← Head:fix/fraudscore-aware-utc📝 Commits (1)
0485fc1fix: use aware timestamp for fraud score updates📊 Changes
1 file changed (+7 additions, -1 deletions)
View changed files
📝
flowsint-enrichers/src/flowsint_enrichers/ip/to_fraudscore.py(+7 -1)📄 Description
Problem: the Scamalytics IP enricher used datetime.utcnow() when setting RiskProfile.last_updated. That helper is deprecated and returns a naive UTC timestamp.
Before / after: before, fraud score updates stored a naive UTC ISO string. After, the timestamp is produced with datetime.datetime.now(datetime.timezone.utc).isoformat(), preserving UTC while including explicit timezone information.
Verification: python -m py_compile flowsint-enrichers\src\flowsint_enrichers\ip\to_fraudscore.py
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.