Redmine
Redmine issue tracker integration — workflow-agnostic CRUD model.
Provides 28 model methods covering issues, projects, statuses, trackers, users, custom fields, relations, versions, time entries, watchers, search, issue categories, journal editing, file uploads, and attachment listing and download. Designed as composable primitives for building any workflow on top of Redmine.
For opinionated Kanban workflows, flow metrics, and sprint reports, see @webframp/redmine-kanban.
Quick Start
swamp extension pull @webframp/redmine
swamp vault create local_encryption redmine # once, if you have no vault yet
swamp vault put redmine API_KEY # prompts; never pass the key inline
swamp model create @webframp/redmine tracker \
--global-arg host=https://your-redmine.example.org \
--global-arg 'apiKey=${{ vault.get("redmine", "API_KEY") }}' \
--global-arg project=your-projectThe project global arg is now optional. Omit it for cross-project queries
(e.g. list_issues with assignedToId: "me" across all projects). Methods
that require a project (list_users, create_issue, list_versions, create_version,
list_issue_categories) throw a clear error if none is provided.
2026.11.03.1
Changed: Bump zod 4.6.5 → 4.6.7
2026.10.21.1
Changed: Documentation only: the README and the registry Quick Start now
store the Redmine API key in a swamp vault (swamp vault put redmine API_KEY)
and wire it with ${{ vault.get("redmine", "API_KEY") }}. The earlier examples
passed apiKey=YOUR_API_KEY, which invited pasting the raw key onto the command
line. The apiKey global argument description says the same.
Upgrade note: No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade, so existing instances need no changes.
Global Arguments
| Argument | Type | Description |
|---|---|---|
| host | string | Redmine instance URL (e.g. https://redmine.example.com) |
| apiKey | string | Redmine API key. Store it in a swamp vault and supply it as ${{ vault.get("redmine", "API_KEY") }}; never pass the literal key |
| project? | string | Default project identifier (omit for cross-project queries) |
| username? | string | Redmine username for X-Redmine-Username header (required by some ingress configurations) |
| Argument | Type | Description |
|---|---|---|
| project? | string | Project identifier (defaults to global project arg) |
| Argument | Type | Description |
|---|---|---|
| project? | string | Project identifier |
| trackerId? | number | Filter by tracker ID |
| statusId? | union | Filter by status ID or open/closed/* |
| assignedToId? | union | Filter by assignee ID or 'me' |
| parentId? | number | Filter by parent issue ID |
| limit? | number | Max results (default 100, max 500) |
| sort? | string | Sort field (e.g., 'updated_on:desc') |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| Argument | Type | Description |
|---|---|---|
| subject | string | Issue subject |
| project? | string | Project identifier |
| trackerId? | number | Tracker ID |
| statusId? | number | Status ID |
| priorityId? | number | Priority ID |
| assignedToId? | number | Assignee user ID |
| description? | string | Issue description |
| parentIssueId? | number | Parent issue ID |
| estimatedHours? | number | Estimated hours |
| customFields? | array | Custom field values |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID to update |
| subject? | string | New subject |
| trackerId? | number | New tracker ID |
| statusId? | number | New status ID |
| priorityId? | number | New priority ID |
| assignedToId? | number | New assignee user ID (null to unassign) |
| description? | string | New description |
| parentIssueId? | number | New parent issue ID |
| estimatedHours? | number | New estimated hours |
| doneRatio? | number | Percent done (0-100) |
| dueDate? | string | Updated due date (YYYY-MM-DD) |
| notes? | string | Journal note to add |
| customFields? | array | Custom field values to update |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID to delete |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Source issue ID |
| issueToId | number | Target issue ID |
| relationType | enum | Relation type |
| delay? | number | Delay in days (for precedes/follows) |
| Argument | Type | Description |
|---|---|---|
| relationId | number | Relation ID to delete |
| Argument | Type | Description |
|---|---|---|
| project? | string | Project identifier (defaults to global project arg) |
| Argument | Type | Description |
|---|---|---|
| issueId? | number | Filter by issue ID |
| project? | string | Filter by project identifier |
| userId? | number | Filter by user ID |
| from? | string | Start date (YYYY-MM-DD) |
| to? | string | End date (YYYY-MM-DD) |
| limit? | number | Max results (default 100, max 500) |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| hours | number | Hours spent |
| activityId? | number | Activity ID |
| comments? | string | Comment |
| spentOn? | string | Date spent (YYYY-MM-DD, defaults to today) |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| userId | number | User ID to add as watcher |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| userId | number | User ID to remove as watcher |
| Argument | Type | Description |
|---|---|---|
| query | string | Search query |
| project? | string | Scope search to project identifier |
| limit? | number | Max results (default 25) |
| Argument | Type | Description |
|---|---|---|
| versionId | number | Version ID |
| Argument | Type | Description |
|---|---|---|
| project? | string | Project identifier (defaults to global project arg) |
| name | string | Version name |
| description? | string | Description |
| status? | enum | Version status |
| dueDate? | string | Due date (YYYY-MM-DD) |
| sharing? | enum | Sharing scope |
| wikiPageTitle? | string | Wiki page title |
| Argument | Type | Description |
|---|---|---|
| versionId | number | Version ID |
| name? | string | New name |
| description? | string | New description |
| status? | enum | New status |
| dueDate? | string | New due date (YYYY-MM-DD) |
| sharing? | enum | New sharing scope |
| wikiPageTitle? | string | New wiki page title |
| Argument | Type | Description |
|---|---|---|
| versionId | number | Version ID to delete |
| Argument | Type | Description |
|---|---|---|
| journalId | number | Journal ID |
| notes | string | Updated notes content |
| privateNotes? | boolean | Mark notes as private |
| Argument | Type | Description |
|---|---|---|
| project? | string | Project identifier (defaults to global project arg) |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID to attach the file to |
| filePath | string | Local file path to upload (relative to working directory) |
| filename? | string | Filename for the attachment (defaults to basename of filePath) |
| description? | string | Attachment description |
| contentType? | string | MIME type (auto-detected from filename if omitted) |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| Argument | Type | Description |
|---|---|---|
| issueId | number | Issue ID |
| attachmentIds? | array | Only these attachment IDs (default: all) |
| contentTypePrefix? | string | Only attachments whose content type starts with this, e.g. image/ (case-insensitive) |
| maxBytes? | number | Skip an attachment larger than this (default 20 MiB) |
Resources
Files
2026.10.21.1
Changed: Documentation only: the README and the registry Quick Start now
store the Redmine API key in a swamp vault (swamp vault put redmine API_KEY)
and wire it with ${{ vault.get("redmine", "API_KEY") }}. The earlier examples
passed apiKey=YOUR_API_KEY, which invited pasting the raw key onto the command
line. The apiKey global argument description says the same.
Upgrade note: No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade, so existing instances need no changes.
2026.10.20.2
Fixed: 2026.10.20.1 gave up on any Retry-After longer than 60 seconds. A
rate limiter with a time window asks for up to the whole window: Skipper's
clusterClientRatelimit over "2m", for example, sends up to about two
minutes. So rate-limited calls failed where earlier versions waited. The cap is
now 300 seconds, and it is also the total that all retries of one request may
wait (so at most 5 minutes, not 4 × the cap). A longer Retry-After (a
maintenance window, a daily quota) still fails fast instead of blocking the
method.
Fixed: 2026.10.20.1 kept X-Redmine-API-Key and X-Redmine-Username on an
http→https redirect to any port of the same host, so a TLS listener on an
unexpected port received the key. Credentials now survive only the default
upgrade, port 80 to 443, which is what a load balancer such as an AWS ALB
issues. A setup that redirects elsewhere gets the set host to … error; set
host to the https URL.
Fixed: A request with a streamed body was resent after a 307/308 redirect or a retryable status, though the first attempt had consumed the stream. A 307/308 now fails with a clear error, and a retryable status is returned at once instead of retried. No built-in method sends a streamed body.
Upgrade note: No schema or globalArguments changes; existing instances
move to this version with an identity upgrade.
2026.10.20.1
Added: list_attachments lists the attachments of an issue (ID, file name,
size, content type, author, date) into a new attachments resource, named
attachments-<issueId>. download_attachments downloads them in one run into a
new attachment file spec, named attachment-<issueId>-<attachmentId>. It
filters by attachment IDs or a content-type prefix (case-insensitive) and skips
files over maxBytes (default 20 MiB). Until now the type had no way to read an
attachment.
The attachments resource always lists every attachment of the issue, with a
status (listed after list_attachments; downloaded, not-selected,
skipped-too-large or failed with an error after download_attachments)
and, for downloaded ones, the dataName of the stored file. filter records
the selection and maxBytes. The size limit applies to the bytes Redmine serves
as well as to the size it records. A non-HTML attachment served as an HTML page
(a login or proxy error page) is failed, not stored. If any download fails,
the method stores the files that did download and the resource, then fails the
run naming each failed attachment.
Fixed: Every request sent X-Redmine-API-Key and X-Redmine-Username to
whatever host a redirect pointed at, because fetch strips only Authorization
on a cross-origin redirect.
Fixed: Methods overwrote each other's stored data. Swamp stores data by
name, not by spec. list_statuses, list_trackers, list_projects,
list_custom_fields, and unfiltered list_issues and list_time_entries all
wrote all. get_issue, create_issue, update_issue, list_relations,
list_time_entries by issue, get_version and create_version wrote bare
numeric IDs, and search wrote the bare sanitized query. list_users,
list_versions, list_time_entries and list_issue_categories wrote the bare
project. Within one method, list_time_entries ignored the user and date
filters, and search mapped foo bar and foo-bar to the same name. Every
data name now carries a spec prefix and every filter (see Upgrade note).
Fixed: The SPDX header in redmine.ts and its test said AGPL-3.0-or-later.
Every source file now says Apache-2.0, matching LICENSE.md and the manifest.
Changed: A redirect to another origin now fails an API call with a message
naming the URL to set as host. A same-origin redirect, or an http→https
upgrade of the same host name on any port, still works. download_attachments
follows other redirects without the credentials (S3 or CDN storage backends).
Changed: Only reads (GET) retry a 502, a 504 or a 503 without Retry-After.
A gateway can time out after Redmine committed a write, so retrying created a
duplicate issue or upload, added a second journal note, or reported a 404 for a
delete that succeeded. Every method still retries a 429, and a 503 that carries
Retry-After (a throttle rejecting before any work), unless the write was
redirected. A Retry-After longer than 60 seconds is no longer slept on (it
blocked the method for up to 4 × the value); the request fails instead. An
HTTP-date Retry-After is now honored. upload_file's upload now uses the same
retry and redirect handling as every other call.
Changed: list_time_entries rejects from and to values that are not
real YYYY-MM-DD dates. Redmine ignored a malformed date and returned
unfiltered entries.
Fixed: The limit descriptions of list_issues and list_time_entries
said "default 25"; the default is 100, the maximum 500.
Changed: Requests no longer wait forever on a server that stops answering.
JSON requests time out after 120 seconds per attempt, downloads after 60 seconds
without data, and upload_file's upload after 10 minutes per attempt.
Upgrade note: Data names change. Update any data.latest(...) or
model.<name>.resource.<spec>.<name> reference:
all→statuses-all,trackers-all,projects-all,custom-fields-all,issues-all,time-entries-all<project>→users-<project>,versions-<project>,issue-categories-<project><filters>→issues-<filters>;<issueId>→issue-<issueId>,relations-<issueId>;<versionId>→version-<versionId>- time entries →
time-entries-<filters>(e.g.time-entries-i:42,time-entries-p:web-u:3); search →search-<query>-<hash>
Data stored under the old names is not migrated; rerun the method to write it
under the new name. No globalArguments changes.
Modified 1 behaviors
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.09.19.1
Fixed: redmineApi/redmineApiPaginated had no retry logic — any 429
(or 502/503/504) failed the request outright. A caller sequentially fetching
many issues (e.g. an enrichment step iterating over a large ticket list) can
trip Redmine's rate limiter even at concurrency 1, and every prior release
turned that into a hard failure. Both helpers now retry through a shared
fetchWithRetry, honoring Retry-After when the server sends one and
falling back to exponential backoff (up to 4 retries) otherwise.
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.19.1
Fixed: redmineApi/redmineApiPaginated had no retry logic — any 429
(or 502/503/504) failed the request outright. A caller sequentially fetching
many issues (e.g. an enrichment step iterating over a large ticket list) can
trip Redmine's rate limiter even at concurrency 1, and every prior release
turned that into a hard failure. Both helpers now retry through a shared
fetchWithRetry, honoring Retry-After when the server sends one and
falling back to exponential backoff (up to 4 retries) otherwise.
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.15.1
Changed: Bump zod 4.4.3 → 4.6.5
2026.08.28.1
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.28.1
Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.
Upgrade note: License text only. No API, schema, or runtime behavior changed.
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.26.3
Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry
quality scorer can resolve dependencies and score the extension. An earlier
release used a bare "zod" import-map specifier, which published but scored as
unscored.
Changed: Retained explicit compilerOptions.strict in deno.json. No
behavioral or schema changes.
2026.08.26.1
Fixed: Added missing description field to upgrade entry for version
2026.08.24.2. The omission caused swamp extension pull to fail with a catalog
validation error ("upgrades.N.description: Invalid input: expected string,
received undefined").
2026.08.25.1
Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.
updated labels
2026.08.24.3
Added: Output metadata attributes for observability.
durationMs: Method execution duration in milliseconds.collectedBy: Extension name that produced the data.fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).
2026.08.24.2
Added Troubleshooting section documenting 500-item pagination cap without truncated field, no retry/degradation, optional project requirement, update_issue re-fetch, upload_file path requirement, and reports/workflows living in separate extension.
2026.08.21.3
Changed:
searchnow rejects an emptyquerywith a clear validation error, instead of sending an empty search to Redmine and writing a resource under an empty instance name.- Redmine API and network-level errors now name the HTTP method and request path (e.g. "Redmine API GET /issues.json failed (500): ..."), instead of only the status code. A connection failure (DNS, refused, timeout) now names the method, path, and host instead of surfacing a bare fetch exception.
upload_filefailures now name the file path and issue id when the file can't be read, and the filename, host, and issue id when the upload itself fails — instead of a bare "Upload failed: <status>" with no indication of what was being uploaded or to where.
2026.08.21.2
Changed: Tightened host and apiKey on the global-args schema, and
subject on create_issue's argument schema, to require non-empty strings.
All three are required identifiers/tokens that the Redmine API never accepts
empty — this catches misconfiguration at model-create/method-call time
instead of a confusing API failure.
2026.08.21.1
Added
- Retroactive compatibility note for the
list_issuesresource instance-name change introduced in2026.08.10.1.
Upgrade note (retroactive — applies to 2026.08.10.1)
Breaking change to list_issues data-resource instance names.
Prior to 2026.08.10.1, list_issues wrote its data resource under the
constant instance name all. Starting with 2026.08.10.1 (PR #343 — make
project global arg optional), the instance name is derived from active filters
using a prefixed scheme to avoid collisions between hyphenated project
identifiers and downstream field values:
| Filter combination | Old instance name | New instance name |
|---|---|---|
| No filters | all |
all (unchanged) |
project only |
all |
p:<project> |
project + parentId |
all |
p:<project>-parent:<parentId> |
project + assignedToId |
all |
p:<project>-a:<assignedToId> |
The table shows representative examples. All active filter arguments
contribute segments in the order: p:, a:, s:, t:, parent:.
Impact: Any data.query expression or workflow step that references the
list_issues resource by its old instance name will fail with an index-out-of-bounds
error after upgrading past 2026.08.10.1.
Recommended consumer pattern: Within workflows, prefer filtering on
workflowRunId rather than name when querying list_issues output. The
workflowRunId predicate is stable across filter and naming changes:
data.query("tracker", "issues", workflowRunId == run.id)2026.08.20.1
Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.
2026.08.21.2
Changed: Tightened host and apiKey on the global-args schema, and
subject on create_issue's argument schema, to require non-empty strings.
All three are required identifiers/tokens that the Redmine API never accepts
empty — this catches misconfiguration at model-create/method-call time
instead of a confusing API failure.
2026.08.21.1
Added
- Retroactive compatibility note for the
list_issuesresource instance-name change introduced in2026.08.10.1.
Upgrade note (retroactive — applies to 2026.08.10.1)
Breaking change to list_issues data-resource instance names.
Prior to 2026.08.10.1, list_issues wrote its data resource under the
constant instance name all. Starting with 2026.08.10.1 (PR #343 — make
project global arg optional), the instance name is derived from active filters
using a prefixed scheme to avoid collisions between hyphenated project
identifiers and downstream field values:
| Filter combination | Old instance name | New instance name |
|---|---|---|
| No filters | all |
all (unchanged) |
project only |
all |
p:<project> |
project + parentId |
all |
p:<project>-parent:<parentId> |
project + assignedToId |
all |
p:<project>-a:<assignedToId> |
The table shows representative examples. All active filter arguments
contribute segments in the order: p:, a:, s:, t:, parent:.
Impact: Any data.query expression or workflow step that references the
list_issues resource by its old instance name will fail with an index-out-of-bounds
error after upgrading past 2026.08.10.1.
Recommended consumer pattern: Within workflows, prefer filtering on
workflowRunId rather than name when querying list_issues output. The
workflowRunId predicate is stable across filter and naming changes:
data.query("tracker", "issues", workflowRunId == run.id)2026.08.20.1
Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.
2026.08.21.1
Added
- Retroactive compatibility note for the
list_issuesresource instance-name change introduced in2026.08.14.1.
Upgrade note (retroactive — applies to 2026.08.14.1)
Breaking change to list_issues data-resource instance names.
Prior to 2026.08.14.1, list_issues wrote its data resource under the
instance name all (or all-<parentId> when a parent filter was active).
Starting with 2026.08.14.1, the instance name is derived from active filters
using a prefixed scheme to avoid collisions between hyphenated project
identifiers and downstream field values:
| Filter combination | Old instance name | New instance name |
|---|---|---|
| No filters | all |
all (unchanged) |
project only |
all |
p:<project> |
project + parentId |
all-<parentId> |
p:<project>-parent:<parentId> |
project + assignedToId |
all |
p:<project>-a:<assignedToId> |
The table shows representative examples. All active filter arguments
contribute segments in the order: p:, a:, s:, t:, parent:.
Impact: Any data.query expression or workflow step that references the
list_issues resource by its old instance name will fail with an index-out-of-bounds
error after upgrading past 2026.08.14.1.
Recommended consumer pattern: Within workflows, prefer filtering on
workflowRunId rather than name when querying list_issues output. The
workflowRunId predicate is stable across filter and naming changes:
data.query("tracker", "issues", workflowRunId == run.id)2026.08.20.1
Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.
2026.08.20.1
Upgrade note: Bumped zod from 4.3.6 to 4.4.3. No behavioral changes — dependency version alignment only.
2026.08.10.1
Changed: The project global argument is now optional. This enables
cross-project queries — most notably list_issues with assignedToId: "me"
across all accessible projects, equivalent to Redmine's /my/page view.
list_issuesandsearchoperate across all projects when no project is specified (neither as a method argument nor globally).- Methods that require a project in their URL path (
list_users,create_issue,list_versions,create_version,list_issue_categories) throw a clear error if none is resolved from either source. - Instance names for
list_issuesnow include all active filter fields with prefixes (p:,a:,s:,t:,parent:) to prevent cache collisions between different filter combinations.
Upgrade: Existing model instances with project set continue to work
unchanged. The upgrade is a no-op identity function (no persisted data
migration needed). New instances may omit project for cross-project queries.
2026.07.18.1
Added: An upgrades array entry (no-op) to redmine.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.
2026.07.09.1
Fixed: Extension failed to load with Last upgrade toVersion "2026.06.21.1" does not match model version "2026.07.08.1" for model type "@webframp/redmine". #194 bumped the model's version field to match the
manifest but never added a matching upgrades entry, leaving the upgrade
chain one version short of the declared model version — a rule the registry
enforces at load time. This adds the missing no-op upgrade entry and bumps the
version again so the chain is complete. No behaviour change beyond #194.
2026.08.10.1
Changed: The project global argument is now optional. This enables
cross-project queries — most notably list_issues with assignedToId: "me"
across all accessible projects, equivalent to Redmine's /my/page view.
list_issuesandsearchoperate across all projects when no project is specified (neither as a method argument nor globally).- Methods that require a project in their URL path (
list_users,create_issue,list_versions,create_version,list_issue_categories) throw a clear error if none is resolved from either source. - Instance names for
list_issuesnow include all active filter fields with prefixes (p:,a:,s:,t:,parent:) to prevent cache collisions between different filter combinations.
Upgrade: Existing model instances with project set continue to work
unchanged. The upgrade is a no-op identity function (no persisted data
migration needed). New instances may omit project for cross-project queries.
2026.07.18.1
Added: An upgrades array entry (no-op) to redmine.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.
2026.07.09.1
Fixed: Extension failed to load with Last upgrade toVersion "2026.06.21.1" does not match model version "2026.07.08.1" for model type "@webframp/redmine". #194 bumped the model's version field to match the
manifest but never added a matching upgrades entry, leaving the upgrade
chain one version short of the declared model version — a rule the registry
enforces at load time. This adds the missing no-op upgrade entry and bumps the
version again so the chain is complete. No behaviour change beyond #194.
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault1/1earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned