Contributor Résumé and Insights

No. Your WordPress.org username is enough. A GitHub token is optional and only raises the API rate limit if you ever hit it; the GitHub section works without one.

No visitor data is ever collected or sent. The plugin only reads your own public contribution data from official WordPress.org endpoints (the plugins, themes, core credits and Photo Directory APIs, your public profile page and support profile) and, if you add a GitHub username, the public GitHub API. Everything is cached locally: profiles and most sources for about a day, core credits of released versions permanently (they never change). Data is refreshed in the background, so the public page itself makes no external requests.

No. Front-end pages render from a local cache with zero external requests.

Yes. Every section can be toggled on or off and reordered, globally in the settings or per block. Sections like GitHub and the grids let you pick exactly what and how much to display.

The block honors your theme's accent color and exposes CSS variables (prefixed --cvr-). You can also copy any template from the plugin's templates/ folder to your-theme/contributor-resume/ and edit it there.

Both. Use the block in the editor and Site Editor, or the [contributor_resume] shortcode anywhere shortcodes run.

Yes. wp cresume refresh rebuilds your résumé snapshot, wp cresume status shows the per-source cache state, and wp cresume clear-cache empties it (one source or all). For the stats, wp cresume stats status shows the state of the collection, wp cresume stats collect runs it, and wp cresume stats keyword-add, keyword-remove and keywords manage the search keywords. Handy on staging or in scripted setups.

From the public WordPress.org APIs: the plugin and theme directories, the download and version stats, the translations and the review feeds of the support forums. They are collected once a day, in the background, and "Collect now" in the Stats tab runs the collection on demand. Downloads come with two years of history. Installs, version adoption and search positions start on the day you turn the stats on, because WordPress.org only publishes their current value. On multisite, each site keeps its own stats.

Yes. Add up to 10 search keywords to each plugin or theme in the Stats tab, and every day the plugin checks where it appears in the WordPress.org search for each one, along with the top 10 of every search. The tags of your plugins are tracked too, with your position and page in each tag.

No. The stats are read directly from the public WordPress.org APIs and stored in your own database. There is no sign-up, no API key and no third-party dashboard, and every view can be exported to CSV.

Yes. In the Emails tab, next to Stats, choose what you want for each schedule: a daily, weekly or monthly email, each one with a summary of the period or only the alerts. Nothing is sent until you turn a schedule on, each administrator sets up their own emails, and you get one email a day at most. The emails are sent by your own site to the address of your user account: there is no mailing service and no sign-up.

Big changes in downloads, active installs moving to another range, new reviews, a change in the average rating, more open support threads and plugins not tested with a new WordPress version. For positions, in searches and in tag pages: entering or leaving the top 10 or the first page, reaching or losing number one, jumps of 3, 5 or 10 places, and which plugin overtook yours or was overtaken by it. You choose which of these you want and for which plugins or themes. Tag pages are read once a week, so their alerts arrive the day each tag is read.

Open the Emails tab, next to Stats, and press "Send me a test email". The emails go out with the mail function of WordPress, like a password reset email, so if those do not arrive either, your site needs an SMTP plugin or a transactional email service. The same screen shows the last email sent and the last error. The emails are sent after the daily collection, which runs with WP-Cron: on a site with very few visits it can run late.

Up to 50 plugins and 50 themes (the ones with the most active installs), and up to 10 search keywords per plugin or theme. Developers can change these limits with the cresume_stats_max_items and cresume_stats_max_keywords filters.

Yes, with a quick look: today's figures and the last 90 days of downloads of any WordPress.org author. It is a snapshot, limited to three different authors a day. It is not kept as history, not exported and not shown in the widget, and it expires after 24 hours. Your own stats keep being collected meanwhile.

They follow the username of your résumé. The plugins and themes of the previous username stop being tracked, but their history stays and comes back if you switch back.

By default it cleans up after itself: its settings, cached data and stats history are removed when you delete the plugin, on every site of a network. If you'd rather keep them for a future reinstall, enable "Keep settings and cached data when the plugin is deleted" in the Advanced settings first.