Add audit log page on website to allow post-mortem review of actions performed by malicious actor

[corneliusroemer]

🏷️ Discussion Type

Product Feedback

Body

Currently, the npm website does not have an audit log feature. There's no way to see what actions were performed at what time. This hampers users' abilities to reconstruct what happened during an attack, like in the axios attack.

Npm should add an audit log page to its website to.

There's a lot of (avoidable) guessing going on in the axios post-mortem because there's no authoritative audit log available: axios/axios#10636 (comment)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[sangtn13]

This is a very important and valid proposal.

Lack of an audit log makes incident response and post-mortem analysis much harder, especially in cases like compromised packages where timeline reconstruction is critical.

An audit log page on npm should include:

• Authentication events (login, token usage, 2FA changes)
• Package actions (publish, unpublish, deprecate, access changes)
• Permission changes (team members, roles)
• Timestamps and IP/device metadata (where possible)

Benefits:

• Faster and more accurate incident investigation
• Improved security transparency for maintainers
• Reduced reliance on guesswork during post-mortems

This would align npm with best practices already seen in other platforms and would be highly valuable for the ecosystem.