@workos-inc/authkit-js MIT 36 versions

@workos-inc/authkit-js

npm Repository Homepage

AuthKit SDK

36

Versions

MIT

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-workosnicknisinickcollisson

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): Legit WorkOS SDK using 0.0.0 as monorepo placeholder version, not throwaway malware pattern.	ai	2026/07/18

Versions (showing 36 of 36)

Version	Deps	Published
0.20.1	0 / 9	2026-06-11
0.20.0	0 / 9	2026-03-24
0.19.0	0 / 9	2026-01-15
0.18.0	0 / 9	2026-01-08
0.17.0	0 / 9	2025-12-23
0.16.0	0 / 9	2025-11-13
0.15.0	0 / 9	2025-11-13
0.14.0	0 / 9	2025-09-17
0.13.0	0 / 9	2025-06-18
0.12.0	0 / 9	2025-05-28
0.11.0	0 / 9	2025-05-21
0.10.1	0 / 9	2025-04-04
0.10.0	0 / 9	2025-03-12
0.9.0	0 / 9	2025-01-15
0.8.1	0 / 9	2025-01-09
0.8.0	0 / 9	2024-12-31
0.7.3	0 / 9	2024-12-11
0.7.2	0 / 9	2024-12-11
0.7.1	0 / 9	2024-12-02
0.7.0	0 / 9	2024-11-11
0.6.1	0 / 8	2024-11-01
0.6.0	0 / 4	2024-10-28
0.5.1	0 / 4	2024-09-14
0.5.0	0 / 4	2024-09-09
0.4.1	0 / 4	2024-08-30
0.4.0	0 / 4	2024-08-30
0.3.0	0 / 4	2024-08-28
0.2.2	0 / 4	2024-08-14
0.2.1	0 / 4	2024-08-12
0.2.0	0 / 4	2024-08-08
0.1.0	0 / 3	2024-08-07
0.0.4	0 / 3	2024-07-22
0.0.3	1 / 3	2024-07-19
0.0.2	1 / 3	2024-07-18
0.0.1	1 / 3	2024-07-18
0.0.0	1 / 3	2024-07-18

v0.20.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.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

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.3

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.1

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.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

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.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-07, 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-07, 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.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

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.2

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.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.