← Home

@oidfed/oidc

npm Repository Homepage

OpenID Connect and OAuth 2.0 federation flows — automatic and explicit client registration, Request Object validation, and RP/OP metadata processing as defined in OpenID Federation 1.0.

7
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

dahkenangnon

Keywords

openid-federationopenid federationtrust chaintrust-chainentity-statementoauth2oidcfederationeidasedugainfederated-identitytrust-marksubordinate-statementtrust-anchorautomatic-registrationexplicit-registrationclient-assertion

Versions (showing 7 of 7)

Version Deps Published
1.0.0 1 / 1
0.5.1 1 / 0
0.5.0 1 / 0
0.4.0 2 / 0
0.3.0 2 / 0
0.2.0 2 / 0
0.1.0 2 / 0

v1.0.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: dahkenangnon → GitHub Actions (on 2026-07-13, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (dahkenangnon) on 2026-07-13, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.