@workos/authkit-session
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation provides stronger supply-chain integrity than gitHead; absence is acceptable for this package. | ai | |
| dependencies | unvetted-dep:iron-session | AI (dependencies): iron-session is a well-established session management library; its use is appropriate and expected in an auth/session package like this one. | ai | |
| dependencies | unvetted-dep:jose | AI (dependencies): jose is the canonical JavaScript JOSE/JWT library; a legitimate dependency for any auth session package. | ai | |
| dependencies | unvetted-dep:@workos-inc/node | AI (dependencies): @workos-inc/node is WorkOS's own official Node.js SDK; expected dependency for a WorkOS auth library. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.5.2 | 3 / 7 | |
| 0.5.1 | 4 / 6 | |
| 0.5.0 | 4 / 6 | |
| 0.4.0 | 4 / 6 | |
| 0.3.4 | 3 / 5 | |
| 0.3.2 | 3 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 4 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.3 | 4 / 5 | |
| 0.1.2 | 4 / 5 | |
| 0.1.1 | 4 / 5 |
v0.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.