UpdateSWH
Check archival state of a source code repository and propose to update it if needed.
As of June 2026, UpdateSWH has 192 users and a 5.00/5 rating from 2 reviews in the Developer Tools category.
Usersup 3.2 percent+3.2%
192
192
Ratingno change0%
5.00
2 reviews
Reviewsno change0%
2
Version
0.9.2
Manifest V3
90-day change · In the last 90 days this extension 3 version updates, changed permissions.
History
8 snapshotsTracking since Apr 23, 2026.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| Apr 23, 2026 | 186 | 5.00 | 2 | 0.6.8 |
| Apr 30, 2026 | 190 | 5.00 | 2 | 0.7.1 |
| May 7, 2026 | 188 | 5.00 | 2 | 0.9.0 |
| May 12, 2026 | 197 | 5.00 | 2 | 0.9.0 |
| May 17, 2026 | 192 | 5.00 | 2 | 0.9.0 |
| May 24, 2026 | 183 | 5.00 | 2 | 0.9.0 |
| Jun 6, 2026 | 192 | 5.00 | 2 | 0.9.0 |
| Jun 15, 2026 | 195 | 5.00 | 2 | 0.9.2 |
| Now | 192 | 5.00 | 2 | 0.9.2 |
Changelog
- Jun 6, 2026description
This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel or via the extension pop-up menu. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/ Version 0.9.0 — Internal rewrite for privacy, reliability and speed - Smaller and faster: the extension bundle is about 80% smaller (jQuery dependency removed, hand-written vanilla JavaScript). - Per forge permission granted by the user, no more <all_urls> permissions.This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel or via the extension pop-up menu. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/ Version 0.9.2 — Support for Gitee forge
- Apr 30, 2026description
This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/ Version 0.7.0 — Internal rewrite for reliability and speed - Smaller and faster: the extension bundle is about 80% smaller (jQuery dependency removed, hand-written vanilla JavaScript). - No changes to how the extension looks or behaves on the page. Settings, permissions, and custom GitLab/Gitea instance lists are preserved.This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel or via the extension pop-up menu. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/ Version 0.9.0 — Internal rewrite for privacy, reliability and speed - Smaller and faster: the extension bundle is about 80% smaller (jQuery dependency removed, hand-written vanilla JavaScript). - Per forge permission granted by the user, no more <all_urls> permissions. - Apr 30, 2026host_permissions
<all_urls>, https://archive.softwareheritage.org/*
https://archive.softwareheritage.org/*
- Apr 30, 2026permissions
storage, tabs, activeTab
storage, tabs, activeTab, scripting
- Apr 23, 2026description
This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/
This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/ Version 0.7.0 — Internal rewrite for reliability and speed - Smaller and faster: the extension bundle is about 80% smaller (jQuery dependency removed, hand-written vanilla JavaScript). - No changes to how the extension looks or behaves on the page. Settings, permissions, and custom GitLab/Gitea instance lists are preserved. - Apr 23, 2026host_permissions
<all_urls>
<all_urls>, https://archive.softwareheritage.org/*
Permissions & access
- Permissions
- storagetabsactiveTabscripting
- Host access
- https://archive.softwareheritage.org/*
Screenshots
About
This extension checks if a software development repository visited by the user in a supported code hosting platform is archived and uptodate in Software Heritage. A color button on the right of the browser indicates if it is uptodate (green), in which case clicking on the button opens a tab on the corresponding page of the archive, missing (grey) or not up to date (yellow), in which case clicking on the button triggers a save code now request, and optionally shows the save request submitted to the Software Heritage archive. A red color indicates that the API request of information for the repository did not succeed: this happens typically when one is visiting a repository that is not publicly accessible, and that naturally cannot be archived. Bitbucket, GitHub, GitLab.com and GitLab instances on domain names of the shape gitlab.*.*, and Gitea instances of the shape gitea.*.* are supported out of the box. GitLab and Gitea instances on other domains can be added in the options panel or via the extension pop-up menu. More documentation is available on the website at https://www.softwareheritage.org/browser-extensions/ Version 0.9.2 — Support for Gitee forge
Technical
- Version
- 0.9.2
- Manifest
- V3
- Size
- 61.16KiB
- Min Chrome
- 88
- Languages
- 1
- Featured
- No
Metadata
- ID
- palihjnakafgffnompkdfgbgdbcagbko
- Developer ID
- u0c2b784be07244459955d54eb8ccfff0
- Developer Email
- [email protected]
- Created
- Jun 28, 2022
- Last Updated (Store)
- Jun 5, 2026
- Last Scraped
- Jun 15, 2026
- Website
- —
- Support URL
- —
- Privacy Policy
- —
Similar extensions
Alternatives to UpdateSWH, ranked by description similarity.
RepoLens
Scan any webpage for GitHub repo links and see repo health at a glance — last update, stars, archived status, and more.
1
GH Page Source Opener
Opens the source of a GH page in a new tab.
2
Github Sidebar
Make shortcuts to repositories you frequently use on Github. Faster navigation and better control over your repositories.
160
★ 4.0
Repo Collector
Instantly see all linked GitHub repositories of any web page and more.
34
★ 5.0
GitHub Last Commit Badge
Adds a last commit badge to GitHub repositories, showing the last commit date.
4
GIT REVEAL
Find the GitHub repository for a site hosted on GitHub pages
28
REFACTORY
GitHub 코드 리뷰를 위한 AI 어시스턴트
2
★ 5.0
코드 리뷰 어시스턴트
GitHub 코드 리뷰를 위한 AI 어시스턴트
3
Data sourced from the Chrome Web Store · last verified Jun 15, 2026.