Publishing Packages Without Long-Lived Tokens: Trusted Publishing with OIDC on npm, PyPI and crates.io
A publish token sitting in a CI secret leaks, expires and is broader than it needs to be. Trusted publishing swaps it for the CI system's OIDC identity and a token that lives for minutes. How npm, PyPI and crates.io differ, a workflow example, the migration order, and the traps around file names, environments, fork pull requests, republishing and the dual-path transition.
The usual way to publish to npm, PyPI or crates.io is to create an API token on the registry and store it as a CI secret. Setup takes five minutes, and then nobody touches it for years. Yet that token can ship code to every machine that installs your package. All three registries now offer the same alternative: trusted publishing. On every run the CI system proves its own identity, and the registry hands back a token that lives for minutes. There is no secret left to store.
Three problems with long-lived tokens
Leaks. A publish token is a bearer secret: it works for whoever holds it, from wherever they are. A variable echoed into a CI log or an .npmrc on someone's laptop is enough, and the token stays valid until revoked.
Expiry. A token that never expires is a liability; one that does expire breaks your release on the worst possible day. npm settled the question: at the end of 2025 classic tokens were permanently revoked, and granular tokens with write access are now capped at 90 days.
Scope. On PyPI an account-wide token can upload to every project on the account. More importantly, no token knows anything about the code using it: anyone with write access to the repository can run a workflow that reads the secret from any branch.
How trusted publishing works
The mechanism is built on OpenID Connect (OIDC):
You register a publisher in the package settings: repository owner, repository name, workflow file name and, optionally, an environment name. No secret is created.
The release job asks the CI system's OIDC provider for a signed identity token (a JWT). On GitHub Actions that takes the id-token: write permission. The token carries the repository, owner, workflow, branch or tag, and environment.
The registry verifies the signature against the provider's public keys, compares the claims with the definition and, if they match, mints a short-lived publish token: 15 minutes on PyPI, 30 on crates.io.
The package is uploaded with that token. The official crates.io action also revokes it when the job finishes.
Identity stops being "anyone who knows this string" and becomes "this workflow, in this repository, in this environment". Trust does not vanish, it moves: anyone who can change the workflow file, or the code running inside it, can now publish.
npm, PyPI and crates.io side by side
npm. Supports GitHub Actions, GitLab CI/CD and CircleCI, but only on cloud-hosted runners. It needs npm CLI 11.5.1 and Node 22.14.0 or later, and npm publish performs the exchange itself. A public package published from a public repository automatically gets provenance tying the version to its workflow run. Three details are easy to miss: repository.url in package.json must match the repository exactly; direct npm publish has to be enabled in the definition (npm stage publish, which waits for manual approval, is always allowed); and a new definition that does not publish successfully within two days expires.
PyPI. The broadest support: GitHub Actions, GitLab CI/CD, Google Cloud and ActiveState. On GitHub you use pypa/gh-action-pypi-publish, which also produces signed attestations for the distribution files by default. A project that does not exist yet can get a pending publisher, but that does not reserve the name; if someone else registers it first, the definition is invalidated.
crates.io. Supports GitHub Actions, plus GitLab CI/CD on GitLab.com as a public beta. A crate's first version must be published with an API token, since trusted publishing can only be set up for existing crates. rust-lang/crates-io-auth-action does the exchange and its token goes to cargo publish as CARGO_REGISTRY_TOKEN. A crate setting can turn token publishing off entirely.
A workflow example
This follows the official Python packaging guide: build and publish run as separate jobs, and only the publish job can request an identity token.
The split is not a matter of taste: the guide does not support building inside the publishing job, which keeps build scripts and dependencies away from the identity token. On npm the job ends with actions/setup-node and npm publish, with no NODE_AUTH_TOKEN anywhere.
Migration order
Define first, publish second, and delete the old token only after the first green release.
Define. Because of npm's two day expiry, create the definition right before the release. Treat the token used for a new crate's first version as single use.
Publish. Add id-token: write and the environment, and take the token out of the workflow without revoking it on the registry yet. Cut a new version.
Verify, then delete. Confirm the release went through OIDC, revoke the token on the registry and close the path: "Require two-factor authentication and disallow tokens" in the npm package settings, the option that requires trusted publishing on crates.io. On PyPI, delete the token in your account settings.
My preference is to start new packages on trusted publishing from day one and to tie the switch for existing ones to their next routine release. The reasoning: the only real risk of the migration is a broken release. A routine release that breaks keeps nobody waiting, while debugging authentication in the middle of an urgent security patch is the worst moment you could pick.
Pitfalls
The workflow file name. The registry knows the workflow by its file name, not by its name: field. A cleanup that renames release.yml to publish.yml silently breaks publishing. npm wants the bare file name with its .yml extension, compares case-sensitively and fails with ENEEDAUTH; PyPI returns invalid-publisher. PyPI does not support reusable workflows (workflow_call), and npm checks the calling workflow rather than the one that publishes.
The environment. If the definition names an environment, the job must run in one with exactly that name. Skipping it is tempting and wrong: none of the three registries has a branch or tag field, so the GitHub environment's deployment rules are where you allow only tags starting with v and add required reviewers. Without one, anyone with write access can publish by running a workflow with the same file name from any branch. Protect release tags with repository rulesets as well.
Pull requests from forks. Workflows running for fork pull requests cannot obtain the upstream repository's OIDC token. The danger is pull_request_target, which runs in the base repository's context with its permissions: if it runs the pull request's code with id-token: write, an outside contribution can publish your package. That is why crates.io blocks pull_request_target and workflow_run from trusted publishing entirely. Trigger the release workflow only on tags or by hand.
Republishing. A version number can be spent only once on all three: npm never accepts a package@version again, even after an unpublish; PyPI rejects any file name used before; crates.io never lets a version be overwritten. Rerunning a job that died halfway produces "already exists" errors. Even the PyPI action's documentation advises against skip-existing for the real PyPI; I would rather bump the version and cut a clean release. Also put the exchange right before the upload, or tests running after it can eat the short lifetime.
The dual-path transition. During the migration both the token and OIDC work, and a green release does not say which was used. If the npm CLI cannot detect an OIDC environment it quietly falls back to a traditional token, so with NODE_AUTH_TOKEN still set, a broken definition goes unnoticed until the day you delete the token. That is why step two removes it from the workflow. To confirm, check "Uploaded using Trusted Publishing?" in the PyPI file details, and, for public repositories, the version's provenance on npm. Deleting a CI secret revokes nothing; copies elsewhere keep working until the token is revoked on the registry.
What it does not solve
Trusted publishing settles who the publisher is, not whether the code deserves trust: provenance proves which repository a package came from, not that its code is harmless. With trust now living in the repository, required reviews, tag rules and actions pinned to full commit hashes are part of publishing security. If you publish from CI you host yourself, you are stuck with tokens; scope them to one project and keep them short-lived.
The easiest publish token to rotate is the one you never created.
[OK] 30 records · 9 featured · 1 retainer · 20 standard
/02 services
services.tree
> note
· Prices are in USD. Volume discounts of 7% for 6-12 day projects and 14% for 13+ day projects apply. Programs of 100+ person-days are priced individually. Prices are negotiable based on scope, urgency and long-term collaboration.
> ls ~/products/ --open-source
[OK] 2 entries · 1 live · 1 pre-release
/03 products
products.list
liveopen source · mit/prod/01
filex
the self-hosted file manager that embeds anywhere
single go binary · vue/react/web-component embed · 5 storage drivers · realtime collab · rbac · native multi-tenancy · mcp server for ai agents
We build infrastructure, automate everything, and keep systems running.
BRF Tech is a Bursa-based DevSecOps and software consulting firm. We operate across 30 service areas, from Kubernetes cluster management to serverless platform setup, CI/CD pipeline design to AI agent development.
What we do is simple: we set up your systems, automate them, and make sure they won't wake you up at 3 AM. We codify your infrastructure with Terraform, move your deployments to GitOps with ArgoCD, and monitor everything with Prometheus. If something breaks — we intervene before it does.
We're against vendor lock-in. We work with open-source tools, self-hosted solutions, and industry-standard technologies. We build your own serverless platform on Knative, isolate with Kata Containers, manage your secrets with Vault. Every project is delivered with clear scope, clear timeline, clear pricing.
DevSecOps & CI/CD
Kubernetes & Serverless
Infrastructure as Code
AI & Agent (MCP/ACP)
Security & Zero Trust
Full-Stack Development
Self-Hosted Solutions
> grep -i question ~/faq.md
[OK] 3 entries · click to expand
[?]What services are included in BRF Tech's DevOps solutions?▾
We offer CI/CD pipeline setup, Kubernetes cluster management, container migration, infrastructure automation with Terraform, monitoring & alerting, in-house technology installations and DevOps consulting services.
[?]What are your software development services?▾
We offer MVP development, existing software performance optimization, backend API development (Node.js, Go, Python) and full-stack application development. Every project is delivered with minimal technical debt.
[?]Which DevOps tools do you work with?▾
From Kubernetes and Docker to Talos Linux, from Terraform and OpenTofu to Ansible, and across Jenkins, GitLab CI/CD, GitHub Actions, ArgoCD, Flux, Helm and Rancher, we work with industry-standard tooling. For observability and error tracking we use Prometheus, Grafana, Loki, Tempo, OpenTelemetry and GlitchTip; for networking, Cilium and Envoy; for test automation, Playwright, Cypress, k6, Locust, Testcontainers and Trivy. We determine the most suitable toolset together, based on your project’s needs.
Automated build, test and deployment pipelines with GitHub Actions, GitLab CI/CD.
Automated build, test and deploy pipeline setup for existing or new repositories. GitHub Actions, GitLab CI/CD or preferred tool is used. Separate workflows are defined for staging + production environments.
Container architecture migration, cluster setup and orchestration.
Production-ready Kubernetes cluster setup on bare-metal or cloud. Includes Helm charts, Ingress, TLS certificate management, namespace isolation and RBAC.
Cozystack is an open-source cloud platform built on Kubernetes and the VMware alternative we recommend most. Virtual machines run on KubeVirt, while managed PostgreSQL, MySQL, Redis and Kafka services and dedicated tenant Kubernetes clusters are provisioned from the same dashboard and API. Includes installation on your own bare-metal servers on Talos Linux, replicated storage with LINSTOR/DRBD, network isolation with Kube-OVN, tenant and quota structure, monitoring, backup and a disaster recovery plan. After deployment we also handle upgrades, operations and support; since the platform is open source, there are no license fees and no vendor lock-in.
Packages
Virtual machine support on an existing Kubernetes cluster with KubeVirt
$2,800
4–6 person-day
Pilot setup (3 nodes, virtual machines + managed database)
$3,500
5–8 person-day
Production setup (HA + replicated storage + monitoring + backup)
$6,500
10–16 person-day
Multi-tenant private cloud (tenants, quotas, managed service catalog)
Planned, low-downtime migration of vSphere/ESXi environments to Cozystack, OpenStack or VHI.
A planned move to a VMware alternative for environments whose costs rose after Broadcom moved VMware licensing to subscription bundles, or whose renewal is coming up. We start with an inventory of your vSphere/ESXi estate (virtual machines, disks, networks, dependencies), then compare today's license cost with the total cost of the target platform. In most environments the target is Cozystack; OpenStack fits large-scale IaaS needs and Virtuozzo Hybrid Infrastructure fits storage-heavy service providers. A pilot runs on non-critical virtual machines, disks are converted with tools such as virt-v2v and Forklift, and the migration proceeds in waves within maintenance windows, with a rollback plan for every step.
Packages
Inventory + cost comparison + migration plan
$2,400
3–5 person-day
Pilot migration (up to 10 virtual machines)
$3,500
5–8 person-day
Phased migration (up to 100 virtual machines)
$9,750
15–22 person-day
Full data center migration (network + storage + backup)
OpenStack deployment, Neutron networking, Ceph/Cinder storage, upgrades and operations.
OpenStack deployment and operations in your own data center. A containerized, highly available control plane with Kolla-Ansible; Nova (compute), Keystone (identity), Glance (images) and Horizon (dashboard). On the network side, Neutron with OVN, VLAN/VXLAN, provider and tenant networks, floating IPs and the Octavia load balancer; on the storage side, Cinder block storage on Ceph RBD and optional S3-compatible object storage. For existing deployments: health checks, planned upgrades between releases, monitoring and alerting setup, and a backup strategy.
Packages
Health check + improvement report (existing deployment)
$2,400
3–5 person-day
Lab / PoC setup (single region, 3 nodes)
$3,500
5–8 person-day
Release upgrade (existing deployment)
$3,900
6–10 person-day
Production setup (HA control plane + Ceph + Neutron/OVN)
Hyperconverged infrastructure: multi-tenant cloud plus block and S3-compatible storage for service providers.
Hyperconverged infrastructure with Virtuozzo Hybrid Infrastructure, where compute, storage and networking run on the same servers. Block, S3-compatible object and NFS storage on software-defined storage, plus backup storage (Backup Gateway) for backup products such as Acronis. For service providers: a multi-tenant cloud with domains and projects, quotas, a self-service panel and an OpenStack-compatible API. Includes hardware sizing, network design, cluster deployment and expansion, version upgrades and operations support.
Packages
Pre-deployment assessment + hardware sizing
$2,400
3–4 person-day
Version upgrade / cluster expansion
$2,800
4–6 person-day
Hyperconverged cluster setup (storage + compute)
$3,900
6–10 person-day
Service provider setup (multi-tenant cloud + S3 + backup storage)
Migration of existing applications to container architecture.
Migration of existing applications to container architecture. Docker image design, Compose configuration and conversion to Kubernetes manifests. Kata Containers / gVisor can be included for advanced isolation.
Health check of your current environment, capacity planning, platform selection and a roadmap.
An independent assessment of your current virtualization environment (VMware vSphere, OpenStack, VHI or other KVM-based platforms). The health check covers cluster configuration, resource overcommit, storage latency, forgotten snapshots, backup and patch status. Capacity planning measures CPU, memory and storage growth to work out the hardware you will need next. Platform selection decides which workload should run where: Cozystack for teams running containers and virtual machines side by side, OpenStack for large-scale IaaS, VHI for storage-heavy service providers; staying on the current platform is also an option for some workloads. The deliverable is a written report with a cost comparison and a prioritized roadmap.
In-house tools like GitLab, Nextcloud, VPN, mail server.
Installation of tools like GitLab, Mattermost, Nextcloud, mail server, VPN, internal monitoring on company servers. Deployed on Docker Compose or Kubernetes.
DB + cache + code bottleneck identification and resolution.
Profiling of existing application, identification and resolution of bottlenecks. DB query optimization, caching layer (Redis), service-level improvements.
MCP/ACP agents, RAG pipelines, multi-agent orchestration, model serving.
LLM integration (OpenAI, Claude, Gemini, local models), tool-augmented AI agents with MCP (Model Context Protocol) and ACP (Agent Communication Protocol). RAG pipeline, multi-agent orchestration, model serving (vLLM/Ollama). AI layer for existing business processes.
Event-driven data pipeline with Apache Kafka, RabbitMQ, NATS. ETL/ELT orchestration with Apache Airflow, real-time data streaming, CDC (Change Data Capture). Data lake/warehouse design, schema registry, dead letter queue management.
Packages
Kafka/RabbitMQ setup + basic producer/consumer
$3,500
5–7 person-day
ETL pipeline (Airflow + source → warehouse)
$5,200
8–12 person-day
Full event-driven architecture (CDC + streaming + DLQ)
Hands-on technical training for your teams. Docker & container fundamentals, Kubernetes operations, Terraform IaC, CI/CD best practices, AI/LLM integration workshops. Practical exercises in live lab environments, content customized by skill level.
E2E test automation with Playwright, Cypress, load testing with k6/Gatling. Pre-deploy quality gate integrated into CI/CD pipeline, test coverage reporting, visual regression testing. Reduce test writing time by up to 60% with AI-assisted test generation.
Your Collected Personal Data, Collection Method and Legal Basis
Any information that identifies or makes you identifiable is considered "personal data." When you visit our website or use our services, contact information such as your name, surname, email address, phone number, as well as your IP address and browser cookie data may be collected through automatic or semi-automatic means. This data is processed based on the legal grounds specified in Article 5 of the Personal Data Protection Law No. 6698: "being directly related to the establishment or performance of a contract" and "being mandatory for the legitimate interests of the data controller, provided that it does not harm the fundamental rights and freedoms of the data subject."
Purpose of Processing Your Personal Data
Your collected personal data is processed for the purposes of providing and improving our services, fulfilling customer requests, meeting legal obligations, conducting information security processes and managing communication activities. Your data is processed in a limited and proportionate manner for the stated purposes; when the purpose ceases to exist, data is deleted, destroyed or anonymized.
To Whom and For What Purposes Collected Personal Data May Be Transferred
Your personal data may be transferred to public institutions and organizations as required by legal regulations, to our business partners and technical infrastructure providers for the purpose of delivering services, and to lawyers and consultants in legal disputes. Transfers are carried out in accordance with Articles 8 and 9 of the Law, with necessary technical and administrative measures in place.
Your Rights as a Data Subject
In accordance with Article 11 of Law No. 6698, you have the right to: learn whether your personal data is being processed; request information if it has been processed; learn the purpose of processing and whether it is used in accordance with its purpose; know the third parties to whom it is transferred domestically or abroad; request correction if it has been processed incompletely or incorrectly; request deletion or destruction within the framework of conditions set out in Article 7 of the Law; request that the operations carried out be notified to third parties to whom data has been transferred; object to any adverse result arising from the analysis of data exclusively through automated systems; and claim compensation for damages in case of unlawful processing. You may contact us through the communication channels on our website to exercise these rights.
Terms & Conditions
Terms & Conditions
1. Service Scope and Changes
BRF Tech conducts its software development, DevOps consulting, infrastructure setup and technical support services within the framework of these terms and conditions. The scope of service is determined separately for each project and finalized through mutual agreement. BRF Tech reserves the right to update the scope, pricing and technical details of its services, provided that prior notice is given.
2. Privacy Policy
Personal data collected within the scope of our services is processed in accordance with our Privacy Policy. For detailed information, please review our Privacy Policy page.
3. Service Usage and Responsibilities
Clients agree to use the provided services solely within legal and ethical boundaries. BRF Tech reserves the right to suspend or terminate services in the event of misuse, violation of third-party rights, or use for illegal activities. The client is responsible for the accuracy and currency of the information provided within the project scope.
4. Payment Terms
Payment terms are determined on a project basis and finalized through mutual agreement at the start of the project. Unless otherwise specified, invoices are payable within 15 days of project delivery. A monthly late payment interest of 2% may apply to overdue payments.
5. Cancellation and Refund Policy
Cancellation requests must be submitted in writing at least 7 days before the service start date. For projects already in progress, billing is based on the proportion of completed work. No refunds are issued for software and infrastructure components specifically developed within the project scope.