← Home

@alloy-js/json

npm Repository Homepage
22
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

bterlson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from manual (bterlson) to GitHub Actions publishing is documented by SLSA attestation; expected for this package. ai
bogus-package bogus-package AI (bogus-package): Missing metadata (description, repo, keywords) is typical for monorepo sub-packages; package has 31 versions, 444 days of history, and a credible Microsoft-affiliated publisher. ai
typosquat typosquat.levenshtein:jsdom AI (typosquat): Scoped package @alloy-js/json is part of the alloy-js framework by Microsoft's bterlson; levenshtein match to jsdom is a false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @alloy-js/json is part of the alloy-js framework by Microsoft's bterlson; levenshtein match to joi is a false positive with no impersonation intent. ai

Versions (showing 22 of 22)

Version Deps Published
0.24.0 2 / 8
0.23.0 2 / 7
0.22.0 2 / 7
0.21.0 2 / 7
0.20.0 2 / 7
0.19.0 2 / 7
0.18.0 2 / 7
0.17.0 2 / 7
0.16.0 2 / 7
0.15.0 2 / 7
0.14.0 2 / 7
0.13.0 2 / 7
0.12.0 2 / 7
0.11.0 2 / 7
0.10.0 2 / 9
0.9.0 2 / 9
0.8.0 2 / 9
0.7.0 2 / 9
0.6.0 2 / 9
0.5.0 2 / 9
0.4.0 2 / 9
0.3.0 2 / 9

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.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.