← Home

@pbvision/schema

npm Repository Homepage

The JS Schema library allows developers to quickly construct [JSON Schema](https://json-schema.org/understanding-json-schema/reference/index.html) and [AWS C2J Shape Schema]() without managing large JSON objects directly. It implements a subset of [the JS

6
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pbvision

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): traverse and json-stable-stringify are well-known, benign utility packages; not a meaningful supply-chain risk. ai
provenance publisher-changed AI (provenance): Publisher change reflects migration to CI/CD-attested publishing (GitHub Actions); SLSA provenance confirms legitimate transition. ai
npm-metadata url-dep:fluent-schema AI (npm-metadata): URL dep is in devDependencies only, pinned to a specific commit hash — not shipped to end users. ai

Versions (showing 6 of 6)

Version Deps Published
0.2.31 4 / 23
0.2.29 4 / 23
0.2.24 4 / 23
0.2.2 2 / 24
0.1.4 2 / 24
0.1.3 2 / 24

v0.2.31

2 findings
HIGH Publisher changed: pbvision → GitHub Actions (on 2026-07-04) provenance

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

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pbvision.

LOW No provenance attestation provenance

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

v0.1.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pbvision.

LOW No provenance attestation provenance

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