← Home

@vertesia/json

npm Repository

JSON utlities

59
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 No source commit

Maintainers

bstefanescuaregnier-vertesialeonruggieromvachette_vertesiahq_commincong-vertesia

Keywords

vertesiajsonutilitieswalkervisitortraversetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from personal account to GitHub Actions CI/CD with SLSA provenance; legitimate and expected for this org. ai
provenance no-provenance AI (provenance): Package has no history of provenance attestation; low-risk utility library with no install scripts. ai
typosquat typosquat.levenshtein:jsdom AI (typosquat): Scoped @vertesia/json package; Levenshtein match to jsdom is a false positive for this legitimate JSON utilities package. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @vertesia/json package; Levenshtein match to joi is a false positive for this legitimate JSON utilities package. ai

Versions (showing 59 of 59)

Version Deps Published
1.4.1 0 / 7
1.4.0 0 / 7
1.3.0 0 / 8
1.2.0 0 / 8
1.1.0 0 / 8
1.0.0 0 / 8
0.82.4 0 / 8
0.82.3 0 / 8
0.82.2 0 / 8
0.82.1 0 / 8
0.82.0 0 / 8
0.81.1 0 / 8
0.81.0 0 / 8
0.80.0 0 / 8
0.79.4 0 / 8
0.79.3 0 / 8
0.79.2 0 / 8
0.79.1 0 / 8
0.79.0 0 / 8
0.78.0 0 / 8
0.77.0 0 / 8
0.76.0 0 / 8
0.75.0 0 / 8
0.74.0 0 / 8
0.73.0 0 / 8
0.72.0 0 / 8
0.71.0 0 / 8
0.70.0 0 / 8
0.69.0 0 / 8
0.68.0 0 / 8
0.67.0 0 / 8
0.66.0 0 / 8
0.65.0 0 / 8
0.64.0 0 / 8
0.63.0 0 / 8
0.62.0 0 / 8
0.61.0 0 / 8
0.60.0 0 / 8
0.59.0 0 / 8
0.58.0 0 / 8
0.57.0 0 / 8
0.56.0 0 / 3
0.55.0 0 / 3
0.54.0 0 / 3
0.52.0 0 / 3
0.51.0 0 / 3
0.50.1 0 / 3
0.50.0 0 / 3
0.49.0 0 / 3
0.48.0 0 / 3
0.47.0 0 / 3
0.46.0 0 / 3
0.45.3 0 / 3
0.45.2 0 / 3
0.45.1 0 / 3
0.45.0 0 / 3
0.44.0 0 / 3
0.43.0 0 / 3
0.42.2 0 / 3

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

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

v0.52.0

1 finding
INFO No provenance attestation provenance

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

v0.51.0

1 finding
INFO No provenance attestation provenance

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

v0.50.1

1 finding
INFO No provenance attestation provenance

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

v0.50.0

1 finding
INFO No provenance attestation provenance

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

v0.49.0

1 finding
INFO No provenance attestation provenance

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

v0.48.0

1 finding
INFO No provenance attestation provenance

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

v0.47.0

1 finding
INFO No provenance attestation provenance

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

v0.46.0

1 finding
INFO No provenance attestation provenance

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

v0.45.3

1 finding
INFO No provenance attestation provenance

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

v0.45.2

1 finding
INFO No provenance attestation provenance

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

v0.45.1

1 finding
INFO No provenance attestation provenance

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

v0.45.0

1 finding
INFO No provenance attestation provenance

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

v0.44.0

1 finding
INFO No provenance attestation provenance

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

v0.43.0

1 finding
INFO No provenance attestation provenance

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

v0.42.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.