👋 We've unified all of GitHub's product documentation in one place! Check out the content for REST API, GraphQL API, and Developers. Learn more on the GitHub blog.
Article version: GitHub.com

Reviewing your security log

You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.

In this article

Were you able to find what you were looking for?

Accessing your security log

The security log lists all actions performed within the last 90 days.

  1. In the upper-right corner of any page, click your profile photo, then click Settings.

    Settings icon in the user bar

  2. In the user settings sidebar, click Security log.

    Security log tab

Searching your security log

The log lists the following information about each action:

  • Which repository an action was performed in
  • The user that performed the action
  • The action that was performed
  • Which country the action took place in
  • The date and time the action occurred

Note that you cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as -, >, or <, match the same format as searching across GitHub. For more information, see "Searching on GitHub."

Search based on operation

Use the operation qualifier to limit actions to specific types of operations. For example:

  • operation:access finds all events where a resource was accessed.
  • operation:authentication finds all events where an authentication event was performed.
  • operation:create finds all events where a resource was created.
  • operation:modify finds all events where an existing resource was modified.
  • operation:remove finds all events where an existing resource was removed.
  • operation:restore finds all events where an existing resource was restored.
  • operation:transfer finds all events where an existing resource was transferred.

Search based on repository

Use the repo qualifier to limit actions to a specific repository. For example:

  • repo:my-org/our-repo finds all events that occurred for the our-repo repository in the my-org organization.
  • repo:my-org/our-repo repo:my-org/another-repo finds all events that occurred for both the our-repo and another-repo repositories in the my-org organization.
  • -repo:my-org/not-this-repo excludes all events that occurred for the not-this-repo repository in the my-org organization.

Note that you must include the account name within the repo qualifier; searching for just repo:our-repo will not work.

Search based on the user

The actor qualifier can scope events based on who performed the action. For example:

  • actor:octocat finds all events performed by octocat.
  • actor:octocat actor:hubot finds all events performed by both octocat and hubot.
  • -actor:hubot excludes all events performed by hubot.

Note that you can only use a GitHub username, not an individual's real name.

Search based on the action performed

Category NameDescription
account_recovery_tokenContains all activities related to adding a recovery token.
billingContains all activities related to your billing information.
marketplace_agreement_signatureContains all activities related to signing the GitHub Marketplace Developer Agreement.
marketplace_listingContains all activities related to listing apps in GitHub Marketplace.
oauth_accessContains all activities related to OAuth Apps you've connected with.
payment_methodContains all activities related to paying for your GitHub subscription.
profile_pictureContains all activities related to your profile picture.
projectContains all activities related to project boards.
public_keyContains all activities related to your public SSH keys.
repoContains all activities related to the repositories you own.
sponsorsContains all events related to GitHub Sponsors and sponsor buttons (see "About GitHub Sponsors" and "Displaying a sponsor button in your repository")
two_factor_authenticationContains all activities related to two-factor authentication.
userContains all activities related to your account.

A description of the events within these categories is listed below.

The account_recovery_token category

ActionDescription
confirmTriggered when you successfully store a new token with a recovery provider.
recoverTriggered when you successfully redeem an account recovery token.
recover_errorTriggered when a token is used but GitHub is not able to validate it.

The billing category

ActionDescription
change_billing_typeTriggered when you change how you pay for GitHub.
change_emailTriggered when you change your email address.

The marketplace_agreement_signature category

ActionDescription
createTriggered when you sign the GitHub Marketplace Developer Agreement.

The marketplace_listing category

ActionDescription
approveTriggered when your listing is approved for inclusion in GitHub Marketplace.
createTriggered when you create a listing for your app in GitHub Marketplace.
delistTriggered when your listing is removed from GitHub Marketplace.
redraftTriggered when your listing is sent back to draft state.
rejectTriggered when your listing is not accepted for inclusion in GitHub Marketplace.

The oauth_access category

ActionDescription
createTriggered when you grant access to an OAuth App.
destroyTriggered when you revoke an OAuth App's access to your account.

The payment_method category

ActionDescription
clearTriggered when a payment method on file is removed.
createTriggered when a new payment method is added, such as a new credit card or PayPal account.
updateTriggered when an existing payment method is updated.

The profile_picture category

ActionDescription
updateTriggered when you set or update your profile picture.

The project category

ActionDescription
createTriggered when a project board is created.
renameTriggered when a project board is renamed.
updateTriggered when a project board is updated.
deleteTriggered when a project board is deleted.
linkTriggered when a repository is linked to a project board.
unlinkTriggered when a repository is unlinked from a project board.
project.accessTriggered when a project board's visibility is changed.
update_user_permissionTriggered when an outside collaborator is added to or removed from a project board or has their permission level changed.

The public_key category

ActionDescription
createTriggered when you add a new public SSH key to your GitHub account.
deleteTriggered when you remove a public SSH key to your GitHub account.

The repo category

ActionDescription
accessTriggered when you a repository you own is switched from "private" to "public" (or vice versa).
add_memberTriggered when a GitHub user is invited to have collaboration access to a repository.
add_topicTriggered when a repository owner adds a topic to a repository.
archivedTriggered when a repository owner archives a repository.
createTriggered when a new repository is created.
destroyTriggered when a repository is deleted.
disableTriggered when a repository is disabled (e.g., for insufficient funds).
enableTriggered when a repository is re-enabled.
remove_memberTriggered when a GitHub user is removed from a repository as a collaborator.
remove_topicTriggered when a repository owner removes a topic from a repository.
renameTriggered when a repository is renamed.
transferTriggered when a repository is transferred.
transfer_startTriggered when a repository transfer is about to occur.
unarchivedTriggered when a repository owner unarchives a repository.

The sponsors category

ActionDescription
repo_funding_link_button_toggleTriggered when you enable or disable a sponsor button in your repository (see "Displaying a sponsor button in your repository")
repo_funding_links_file_actionTriggered when you change the FUNDING file in your repository (see "Displaying a sponsor button in your repository")
sponsor_sponsorship_cancelTriggered when you cancel a sponsorship (see "Downgrading a sponsorship")
sponsor_sponsorship_createTriggered when you sponsor a developer (see "Sponsoring an open source contributor")
sponsor_sponsorship_preference_changeTriggered when you change whether you receive email updates from a sponsored developer (see "Managing your sponsorship")
sponsor_sponsorship_tier_changeTriggered when you upgrade or downgrade your sponsorship (see "Upgrading a sponsorship" and "Downgrading a sponsorship")
sponsored_developer_approveTriggered when your GitHub Sponsors account is approved (see "Setting up GitHub Sponsors for your user account")
sponsored_developer_createTriggered when your GitHub Sponsors account is created (see "Setting up GitHub Sponsors for your user account")
sponsored_developer_profile_updateTriggered when you edit your sponsored developer profile (see "Editing your profile details for GitHub Sponsors")
sponsored_developer_request_approvalTriggered when you submit your application for GitHub Sponsors for approval (see "Setting up GitHub Sponsors for your user account")
sponsored_developer_tier_description_updateTriggered when you change the description for a sponsorship tier (see "Changing your sponsorship tiers")
sponsored_developer_update_newsletter_sendTriggered when you send an email update to your sponsors (see "Contacting your sponsors")
waitlist_invite_sponsored_developerTriggered when you are invited to join GitHub Sponsors from the waitlist (see "Setting up GitHub Sponsors for your user account")
waitlist_joinTriggered when you join the waitlist to become a sponsored developer (see "Setting up GitHub Sponsors for your user account")

The successor_invitation category

ActionDescription
acceptTriggered when you accept a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
cancelTriggered when you cancel a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
createTriggered when you create a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
declineTriggered when you decline a succession invitation (see "Maintaining ownership continuity of your user account's repositories")
revokeTriggered when you revoke a succession invitation (see "Maintaining ownership continuity of your user account's repositories")

The two_factor_authentication category

ActionDescription
enabledTriggered when two-factor authentication is enabled.
disabledTriggered when two-factor authentication is disabled.

The user category

ActionDescription
add_emailTriggered when you add a new email address.
createTriggered when you create a new user account.
remove_emailTriggered when you remove an email address.
renameTriggered when you rename your account.
change_passwordTriggered when you change your password.
forgot_passwordTriggered when you ask for a password reset.
loginTriggered when you log in to GitHub.
failed_loginTriggered when you failed to log in successfully.
two_factor_requestedTriggered when GitHub asks you for your two-factor authentication code.
show_private_contributions_countTriggered when you publicize private contributions on your profile.
hide_private_contributions_countTriggered when you hide private contributions on your profile.
report_contentTriggered when you report an issue or pull request, or a comment on an issue, pull request, or commit.

The user_status category

ActionDescription
updateTriggered when you set or change the status on your profile. For more information, see "Setting a status."
destroyTriggered when you clear the status on your profile.

Exporting your security log

You can export the log as JSON data or a comma-separated value (CSV) file.

Export button

To filter the results in your export, search by one or more of these supported qualifiers before using the Export drop-down menu.

QualifierExample value
actionteam.create
actoroctocat
usercodertocat
orgocto-org
repoocto-org/documentation
created2019-06-01

After you export the log as JSON or CSV, you'll see the following keys and values in the resulting file.

KeyExample value
actionteam.create
actoroctocat
usercodertocat
orgocto-org
repoocto-org/documentation
created_at1429548104000 (Timestamp shows the time since Epoch with milliseconds.)
data.hook_id245
data.events["issues", "issue_comment", "pull_request", "pull_request_review_comment"]
data.events_were["push", "pull_request", "issues"]
data.target_loginoctocat
data.old_userhubot
data.teamocto-org/engineering

Were you able to find what you were looking for?

Ask a human

Can't find what you're looking for?

Contact us