← Home

@atproto/jwk

npm Repository Homepage
16
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 16 of 16)

Version Deps Published
0.7.4 2 / 0
0.7.3 2 / 0
0.7.2 2 / 0
0.7.1 2 / 0
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
0.1.5 2 / 1
0.1.4 2 / 1
0.1.3 2 / 1
0.1.2 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1

v0.7.4

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

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

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.