Skip to content

fix: guard against malformed/non-array history data in fetchUserInfo #261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jagdish-15 merged 1 commit into from
Jun 28, 2026
+3 −1
Merged

fix: guard against malformed/non-array history data in fetchUserInfo #261

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion scripts/fetch-user-info.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ async function fetchUserInfo(username) {
// Auto-Migration Check & Routing
if (Array.isArray(data)) {
history = data;
} else {
} else if (data && typeof data === "object") {
// Safe object destructuring for the new profile structure
history = data.history || [];
badges = data.badges || [];
Expand Down Expand Up @@ -69,6 +69,8 @@ async function fetchUserInfo(username) {
await Promise.allSettled([livePromise]);

// Ensure history is sorted chronologically
// Guard against a corrupted history file (e.g. non-array `history` field)
history = Array.isArray(history) ? history : [];
history.sort((a, b) => new Date(a.date) - new Date(b.date));

return {
Expand Down
Loading