@workos-inc/authkit-react No license 30 versions

@workos-inc/authkit-react

npm Repository Homepage

30

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mthadley-workosmark-workosgrinichnpm-workoscameron-workosgjtorikianchance-workospeakematt-workosgioworkosnicknisilucasmotta.workosnickcollisson

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): WorkOS org uses 0.0.0 as initial release version; established package with 170k weekly downloads.	ai	2026/06/04
provenance	publisher-changed	AI (provenance): Migrated from individual publisher to GitHub Actions CI/CD with SLSA provenance; expected for workos org.	ai	2026/05/13
dependencies	unvetted-dep:@workos-inc/authkit-js	AI (dependencies): First-party WorkOS dependency; same publisher org, expected runtime dep for this SDK.	ai	2026/05/13

Versions (showing 30 of 30)

Version	Deps	Published
0.16.1	1 / 5	2026-03-26
0.16.0	1 / 5	2026-01-15
0.15.1	1 / 5	2026-01-13
0.15.0	1 / 5	2025-12-24
0.14.0	1 / 5	2025-12-12
0.13.0	1 / 5	2025-09-18
0.12.0	1 / 5	2025-09-03
0.11.0	1 / 5	2025-06-19
0.10.0	1 / 5	2025-05-21
0.9.1	1 / 5	2025-04-15
0.9.0	1 / 5	2025-01-15
0.8.1	1 / 5	2025-01-09
0.8.0	1 / 5	2025-01-01
0.7.2	1 / 5	2024-12-13
0.7.1	1 / 5	2024-12-03
0.7.0	1 / 5	2024-11-12
0.6.0	1 / 5	2024-11-01
0.5.1	1 / 5	2024-09-16
0.5.0	1 / 4	2024-09-09
0.4.1	1 / 4	2024-08-30
0.4.0	1 / 4	2024-08-30
0.3.2	1 / 4	2024-08-14
0.3.1	1 / 4	2024-08-12
0.3.0	1 / 4	2024-08-08
0.2.0	1 / 4	2024-08-07
0.1.2	1 / 4	2024-08-01
0.1.1	1 / 4	2024-07-24
0.1.0	1 / 4	2024-07-23
0.0.1	1 / 4	2024-07-18
0.0.0	1 / 4	2024-07-18

v0.16.1

1 finding

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.

v0.16.0

2 findings

HIGH Publisher changed: nicknisi → GitHub Actions (on 2026-01-15) provenance

This version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.

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.

v0.15.1

2 findings

HIGH Publisher changed: nicknisi → GitHub Actions (on 2026-01-13) provenance

This version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.

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.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: cameron-workos → npm-workos (on 2024-08-12, known maintainer) provenance

This version was published by a different npm account (npm-workos) than the most recent previously approved version (cameron-workos) on 2024-08-12, but npm-workos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.3.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: cameron-workos → npm-workos (on 2024-08-08, known maintainer) provenance

This version was published by a different npm account (npm-workos) than the most recent previously approved version (cameron-workos) on 2024-08-08, but npm-workos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.