As for details about the issue, I just finished chatting with primary developer for peakd, and he told me this:

Header is computed from
curl -s --data '{"id":4,"jsonrpc":"2.0","method":"call","params":["database_api","get_accounts",[["wochenblick"]]]}' https://api.hive.blog
11:12 AM
Posts is from
curl -s --data '{"id":5,"jsonrpc":"2.0","method":"bridge.get_account_posts","params":{"sort":"blog","account":"wochenblick","limit":1,"start_author":null,"start_permlink":null,"observer":"asgarth-dev"}}' https://api.hive.blog
Seems to be a different value at the API level

The actual issue is that the first call goes to hived (blockchain node), which has correct value, and the second call goes to hivemind (which has the bug that causes it to compute wrong value).

This has been confirmed by our hivemind tech lead, wrona, who reports:

dan
9:45 AM
Ok, so the weird thing for me is that peakd.com reports 60 rep for this user on profile, but 2 for articles. Both peakd.com and condenser are using api.hive.blog. So it seems like peakd uses different source for this data in it's profile.
So both report 2 for rep beside the articles
This may just be a problem with peakd. I'll ask peakd guys about it.
wrona
10:03 AM
yes seems so. api.hive.blog returns negative rep. for wochenblick where hive-2 instance returns: 9863690427572 (hived 9859483834254)
dan
11:17 AM
yep, I just confirmed that peakd uses two different API calls (one to hivemind, one to hived), and that's why they show the two separate values.