← Perma Archiver on the catalogue
Source: zoteroplugins.org

Plugin review sheet: Perma Archiver

Last checked 18 Nov 2026 · zoteroplugins.org/p/zotero-perma-archiver

Identity

Developer
kirinccchang
Repository
github.com/kirinccchang/zotero-perma-archiver
Licence
AGPL-3.0
Version checked
v1.3.2, released 10 Apr 2026
File
perma-archiver_v1.3.2.xpi (0.01 MB)
SHA-256 of file
9b748ce32dc7a49b7bd16c1296d9f7bc4dac142780e1a70a9394c862f69d7540
Add-on ID
[email protected]
Updates
Updates come from this project's GitHub repository: https://raw.githubusercontent.com/kirinccchang/zotero-perma-archiver/main/update.json

Works with

Zotero 7–10, 11 beta. It works with the current Zotero (10).

Its release lists Zotero 7–8; its update file extends support to later versions.

A

Zotero Plugins grade: A, recommended

Because every code check came out low. Next rung: A+, once we've tested it installed in Zotero 10.

Applies to v1.3.2, released 10 Apr 2026. How we grade

What we found in the code

  • Code transparencyNot checked yet

    Readable code; not yet checked against the published source. The developer uploaded the release file from the kirinccchang account. We haven't yet checked whether this file matches the public source code.

    UpdatesUpdates come from this project's GitHub repositoryThe update address offers this version
  • Where your data goesLow concern

    We found: only contacts services we could identify. 2 addresses in 2 groups.

    Scholarly services (1)perma.cc (named in its code)
    Apps you connect (1)api.perma.cc

    Where we found it: api.perma.cc (content.js · line 20).

  • Powerful capabilitiesLow concern

    Stores API keys or passwords

    Low concern (1)Stores API keys or passwords

Live test, maintenance and what it needs

Live test
Code checked · not yet tested in a live Zotero
Maintenance
Slowing down · last release 10 Apr 2026, 1 contributor
What it needs
An API key (Needs a key you get from the service (Perma.cc). What needs it: A perma.cc API key is needed to archive anything.)

What this sheet is

We read the code of a plugin's latest release. Three things set the grade: whether the code can be read, where your data goes, and what powerful capabilities it uses. For an A+, we also install it in a fresh copy of Zotero and record every server it contacts. Reading code shows what a plugin could do.

This sheet summarises those checks for the release named above. It is not a security audit and not a guarantee. Compiled code can't be read like the rest of a plugin, so our checks can't see what it does. Each new release is checked again: check the date and version. Every finding, with its file and line, is at zoteroplugins.org/p/zotero-perma-archiver.