@xyo-network/diviner-jsonpath-memory
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Large established monorepo package; sparse README/keywords are consistent across all versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher xyo has 2418 approved packages; dormancy likely reflects monorepo release cadence, not account takeover. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): Package has always been LGPL-3.0-only; stable license choice for this package. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 6.0.4 | 3 / 31 | |
| 6.0.3 | 3 / 32 | |
| 6.0.2 | 3 / 32 | |
| 6.0.1 | 3 / 36 | |
| 6.0.0 | 3 / 40 | |
| 5.6.4 | 3 / 40 | |
| 5.6.1 | 3 / 42 | |
| 5.5.6 | 3 / 43 | |
| 5.5.5 | 3 / 43 | |
| 5.5.4 | 3 / 43 | |
| 5.5.3 | 3 / 50 | |
| 5.5.2 | 0 / 60 | |
| 5.5.1 | 0 / 60 | |
| 5.5.0 | 0 / 60 | |
| 5.4.1 | 2 / 40 | |
| 5.4.0 | 2 / 40 | |
| 5.3.30 | 2 / 42 | |
| 5.3.27 | 6 / 23 | |
| 5.3.26 | 6 / 25 | |
| 5.3.25 | 6 / 25 | |
| 5.3.22 | 6 / 28 | |
| 5.3.17 | 6 / 10 | |
| 5.3.16 | 6 / 10 | |
| 5.3.15 | 6 / 10 | |
| 5.3.14 | 6 / 10 | |
| 5.3.13 | 6 / 10 | |
| 5.3.12 | 6 / 10 | |
| 5.3.11 | 6 / 10 | |
| 5.3.10 | 6 / 10 | |
| 5.3.8 | 6 / 10 | |
| 5.3.7 | 6 / 10 | |
| 5.3.6 | 6 / 9 | |
| 5.3.5 | 6 / 9 | |
| 5.3.4 | 6 / 9 | |
| 5.3.3 | 7 / 8 | |
| 5.3.2 | 7 / 8 | |
| 5.3.1 | 7 / 8 | |
| 5.3.0 | 7 / 8 | |
| 5.2.27 | 7 / 8 | |
| 5.2.25 | 7 / 8 | |
| 5.2.19 | 7 / 8 | |
| 5.2.18 | 7 / 8 | |
| 5.2.17 | 7 / 8 | |
| 5.2.16 | 7 / 8 | |
| 5.2.14 | 7 / 8 | |
| 5.2.13 | 7 / 8 | |
| 5.2.12 | 7 / 8 | |
| 5.2.11 | 7 / 8 | |
| 5.2.10 | 7 / 8 | |
| 5.2.9 | 7 / 8 | |
| 5.2.8 | 7 / 8 | |
| 5.2.7 | 7 / 8 | |
| 5.2.6 | 7 / 8 | |
| 5.2.5 | 7 / 8 | |
| 5.2.1 | 7 / 8 | |
| 5.2.0 | 7 / 8 | |
| 5.1.24 | 7 / 8 | |
| 5.1.21 | 7 / 8 | |
| 5.1.20 | 7 / 8 | |
| 5.1.18 | 7 / 8 | |
| 5.1.17 | 7 / 8 | |
| 5.1.16 | 7 / 8 | |
| 5.1.14 | 7 / 8 | |
| 5.1.13 | 7 / 8 | |
| 5.1.10 | 7 / 8 | |
| 5.1.9 | 7 / 8 | |
| 5.1.7 | 7 / 8 | |
| 5.1.2 | 7 / 8 | |
| 5.1.1 | 7 / 8 | |
| 5.1.0 | 7 / 8 | |
| 5.0.7 | 7 / 8 | |
| 5.0.6 | 7 / 8 | |
| 5.0.5 | 7 / 8 | |
| 5.0.4 | 7 / 8 | |
| 5.0.3 | 7 / 8 | |
| 5.0.2 | 7 / 8 | |
| 5.0.1 | 7 / 8 | |
| 5.0.0 | 7 / 8 |
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-05, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.30
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.26
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.25
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.