← Home

@yotoplay/prettier

A collection of common prettier settings used by our APIs

4
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

yoto-robbealaistynavikkio88erixkyoto_ralphhiro11hasan-yotoadamflitneyjaimen-yotoseb.simtami.effendowiczliam-yotoyusyuan-yotoowarwayonishiwebtash.mullafilipyotoalvinometricemmabeynongregyototomhazledinetheresa-yo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package uses semantic-release via GitHub Actions CI/CD; publisher being 'GitHub Actions' is the expected automated publishing pattern for this org. ai

Versions (showing 4 of 4)

Version Deps Published
2.7.2 0 / 8
2.7.1 0 / 8
2.7.0 0 / 8
2.6.0 0 / 8

v2.7.2

2 findings
HIGH Publisher changed: yoto-robbeal → GitHub Actions (on 2026-05-20) provenance

This version was published by a different npm account than previous versions on 2026-05-20. 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.

v2.7.1

2 findings
HIGH Publisher changed: yoto-robbeal → GitHub Actions (on 2026-05-20) provenance

This version was published by a different npm account than previous versions on 2026-05-20. 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.

v2.7.0

2 findings
HIGH Publisher changed: yoto-robbeal → GitHub Actions (on 2026-05-20) provenance

This version was published by a different npm account than previous versions on 2026-05-20. 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.