← Home

@dprint/json

npm Repository Homepage
5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dsherret

Keywords

jsoncodeformatterdprint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from dsherret to GitHub Actions CI is documented by SLSA provenance; legitimate automation handoff for this package. ai
source-diff source-size-dropped AI (source-diff): Package ships compiled WASM binary; source size drop reflects build artifact distribution, not code removal. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is standard WASM buffer handling for this formatter plugin; not obfuscation. ai
typosquat typosquat.levenshtein:jsdom AI (typosquat): Scoped @dprint/json is a legitimate dprint formatter plugin, not a typosquat of jsdom. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @dprint/json is a legitimate dprint formatter plugin, not a typosquat of joi. ai

Versions (showing 5 of 5)

Version Deps Published
0.21.3 0 / 1
0.21.2 0 / 1
0.21.1 0 / 1
0.21.0 0 / 1
0.15.6 0 / 1

v0.21.3

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

2 findings
HIGH Publisher changed: dsherret → GitHub Actions (on 2026-03-20) provenance

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

v0.21.1

2 findings
HIGH Publisher changed: dsherret → GitHub Actions (on 2025-12-31) provenance

This version was published by a different npm account than previous versions on 2025-12-31. 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.21.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.6

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.