← Home

@jsonforms/core

12
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

sdirixmkoegeltortmayreugenneufeldjfaltermeierjsonforms-publishlkoehler

Keywords

formformsjsonjsonformsfrontendgeneratorinputvalidationrenderenginejsonschemaschemauischemalayoutcustomization

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/json-schema AI (phantom-deps): Types package used by convention, not directly imported; benign. ai
provenance missing-githead AI (provenance): Expected artifact of CI/CD publish migration, offset by SLSA provenance attestation. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Legitimate @jsonforms/core package; Levenshtein match to 'cors' is a false positive for this scoped package. ai

Versions (showing 12 of 12)

Version Deps Published
3.8.0 4 / 25
3.7.0 4 / 25
3.6.0 4 / 26
3.5.1 4 / 26
3.5.0 4 / 26
3.4.1 4 / 26
3.4.0 4 / 26
3.3.0 4 / 26
3.2.1 4 / 26
3.2.0 4 / 26
3.1.0 4 / 26
3.0.0 4 / 20

v3.5.1

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.

v3.5.0

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.

v3.4.1

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.

v3.4.0

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.

v3.3.0

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.

v3.2.1

3 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: jsonforms-publish.

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.

INFO Publisher changed: sdirix → jsonforms-publish (on 2024-01-24, now via trusted publisher with provenance) provenance

This version was published by a different npm account (jsonforms-publish) than the most recent previously approved version (sdirix) on 2024-01-24, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v3.2.0

3 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: jsonforms-publish.

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.

INFO Publisher changed: sdirix → jsonforms-publish (on 2024-01-23, now via trusted publisher with provenance) provenance

This version was published by a different npm account (jsonforms-publish) than the most recent previously approved version (sdirix) on 2024-01-23, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

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

v3.0.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.