@atproto-labs/pipe
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
atprototransformer
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): bluesky-social/atproto monorepo migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate origin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with org-level CI publishing transition for the atproto monorepo. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @atproto-labs/pipe is part of the official ATProto/Bluesky ecosystem; 'pipe' is a common FP term, not a typosquat of 'vite'. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped package @atproto-labs/pipe is part of the official ATProto/Bluesky ecosystem; 'pipe' is a common FP term, not a typosquat of 'pino'. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher (devinivy) with strong track record; lack of provenance is common and not a risk signal for this package. | ai |
v0.2.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.1.1
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.