← Home

@atproto/jwk

npm Repository Homepage
6
Versions
—
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

dholmspfrazeedevinivyestrattonbaileymatthieu-bluesky

Keywords

atprotojwkjwksjwtjson web key

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Bluesky/atproto monorepo migrated to GitHub Actions CI publishing with SLSA attestation; expected for this org. ai
maintainer-change maintainer-added AI (maintainer-change): matthieu-bluesky is a known atproto contributor; addition aligns with org-level maintainer management. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @atproto/jwk is a JWK cryptography library in the Bluesky ATProto ecosystem; no relation to joi. Levenshtein match is a false positive that will recur on every version. ai

Versions (showing 6 of 6)

Version Deps Published
0.7.0 2 / 1
0.6.0 2 / 1
0.5.0 2 / 1
0.4.0 2 / 1
0.3.0 2 / 1
0.2.0 2 / 1

v0.7.0

2 findings
HIGH Publisher changed: devinivy → GitHub Actions (on 2026-05-19) provenance

This version was published by a different npm account than previous versions on 2026-05-19. 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.6.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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