← Home

@atproto-labs/fetch

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

devinivyestrattonbaileydholms

Keywords

atprotofetch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): bluesky-social/atproto monorepo migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern going forward. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer consolidation consistent with org-level CI publishing transition for this monorepo package. ai
provenance no-provenance AI (provenance): Established atproto-labs package from a long-standing publisher; lack of provenance is common and not a risk signal here. ai

Versions (showing 2 of 2)

Version Deps Published
0.3.0 1 / 1
0.2.3 1 / 1

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