@alloy-js/json
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.23.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.