← Home

@atproto/did

npm Repository Homepage
8
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

atprotodidvalidationtypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from devinivy to GitHub Actions reflects CI/CD automation of releases from the official bluesky-social/atproto repo, confirmed by SLSA provenance attestation. Legitimate supply chain improvement. ai
provenance slsa-provenance AI (provenance): SLSA provenance attestation is a positive signal; stable for this package published via official bluesky-social/atproto CI. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): @atproto/did is a legitimate scoped package in the atproto ecosystem; Levenshtein match to 'uuid' is a spurious false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:zod AI (typosquat): @atproto/did is a legitimate scoped package in the atproto ecosystem; Levenshtein match to 'zod' is a spurious false positive with no impersonation intent. ai

Versions (showing 8 of 8)

Version Deps Published
0.5.0 1 / 3
0.4.0 1 / 3
0.3.0 1 / 3
0.2.4 1 / 3
0.2.3 1 / 3
0.2.2 1 / 3
0.2.1 1 / 3
0.2.0 1 / 3

v0.5.0

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

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

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