← Home

@transloadit/prettier-bytes

> Even though this module is publicly accessible, we do not recommend using it in projects outside of [Transloadit](https://transloadit.com). We won't make any guarantees about its workings and can change things at any time, we won't adhere strictly to Se

2
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

kvzmifiremcohaszing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance for transloadit org. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by monorepo consolidation; SLSA provenance confirms legitimate CI publish. ai
bogus-package bogus-package AI (bogus-package): Minimal utility package in a monorepo; low-value signals are false positives. ai

Versions (showing 2 of 2)

Version Deps Published
2.0.0 0 / 0
1.1.0 0 / 0

v2.0.0

2 findings
HIGH Publisher changed: kvz → GitHub Actions (on 2026-05-28) provenance

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

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