docs: add certforge-issuer to external issuers listUpdate issuers.md

[CertForge100]

Adds certforge-issuer to the list of known external cert-manager issuers.

What is certforge-issuer?

certforge-issuer bridges cert-manager to CertForge's policy engine. It adds governance controls cert-manager doesn't provide natively:

• Domain Trust Profiles — define which CAs, SANs, and wildcard patterns are valid per domain
• Approval workflows — route certificate requests to a human approver before issuance
• Policy enforcement — requests that don't match a Trust Profile are denied before reaching a CA
• Audit trail — every request, approval, and renewal is logged with actor, timestamp, and outcome

Existing cert-manager Certificate resources require no changes — certforge-issuer is added as the issuerRef and governance is in place immediately.

Links

• GitHub: https://github.com/CertForge-LLC/certforge-issuer
• CertForge: https://certgovernance.app
• License: Apache 2.0

Tier: 🥈 — released within 12 months, open source

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign erikgb for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for cert-manager ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	64ef9ca
🔍 Latest deploy log	https://app.netlify.com/projects/cert-manager/deploys/6a31328bd3ef8b0008c2dac3
😎 Deploy Preview	https://deploy-preview-2118--cert-manager.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

Adds certforge-issuer to the cert-manager external issuers documentation list, including the required reference links for docs, CA/provider site, and release page.

Changes:

• Added a new 🥈 tier table entry for certforge-issuer.
• Added reference link definitions for config:certforge-issuer, ca:certforge-issuer, and release:certforge-issuer.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[wallrj-cyberark]

Thank you for submitting this. A few items need addressing before this can move forward.

CI failure

The spelling check fails — certforge needs to be added to .spelling. (See #2130 for a recent example where solidserver was added.)

Formatting

The PR removes blank lines between the reference link sections (between [config:...] and [//]: # (CA docs), and between [ca:...] and [//]: # (Release pages)). These section separators should be preserved — compare with the existing file structure.

PR title

The title appears to have a concatenation error: ...external issuers listUpdate issuers.md — "listUpdate" should be two separate words or just "list".

Project maturity

The certforge-issuer repository was created on 20 May 2026 (less than a month ago) with 0 stars, 0 forks, 15 commits, and no open-source licence. The first release (v0.1.0) was cut on 22 May and this PR was opened on 29 May — the same day as the v0.1.1 release.

While the 🥈 tier criteria only require "a release in the last 12 months" (which is technically met), the project has no licence file, which means the code is legally all-rights-reserved. That is a concern for listing it as a cert-manager integration — users cannot legally use or modify the code without an explicit licence grant.

Non-functional product links

The PR adds a [ca:certforge-issuer] link pointing to certgovernance.app. I checked the linked product infrastructure:

• Docs (docs.certforge.xyz) — returns HTTP 403 Forbidden
• Signup (app.certforge.xyz/signup) — connection refused (nothing listening)
• Self-hosted repo (github.com/certforge/self-hosted, linked from the landing page) — returns 404, repository does not exist

The issuer is a proxy to this SaaS product, which does not appear to be operational. Listing it on the cert-manager website would direct users to a product they cannot actually use.

Could you:

1. Add an open-source licence to the certforge-issuer repository
2. Ensure the product links are functional before requesting a listing
3. Fix the CI failure (.spelling)
4. Restore the blank line separators between reference link sections
5. Fix the PR title

[maelvls]

Hey. Nothing to do with your PR, but I've noticed some dead links on https://certgovernance.app/:

• https://app.certforge.xyz/login returns tlsv1 alert internal, alert number 80
• https://app.certforge.xyz/signup returns tlsv1 alert internal, alert number 80
• https://docs.certforge.xyz/self-hosted/quick-start shows "CNAME Cross-User Banned"

Update: links have been updated, they all work now.