@xylabs/exists
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer, matches publisher-changed-known-maintainer INFO finding. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is a known/matched account, not compromise indicator. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org maintainer rotation, no takeover evidence. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deprecation shim intentionally re-exports from @ariestools/sdk, same org/version, as documented. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): LGPL-3.0-only is the established license for this package across all versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (210 approved); no material changes in this version; dormancy likely reflects normal release cadence gaps. | ai |
Versions (showing 100 of 131)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 1 / 10 | |
| 8.0.1 | 1 / 10 | |
| 8.0.0 | 1 / 10 | |
| 7.0.8 | 1 / 10 | |
| 7.0.7 | 1 / 10 | |
| 7.0.6 | 1 / 10 | |
| 7.0.5 | 1 / 10 | |
| 7.0.4 | 1 / 10 | |
| 7.0.2 | 0 / 8 | |
| 7.0.1 | 0 / 8 | |
| 7.0.0 | 0 / 8 | |
| 6.1.4 | 0 / 8 | |
| 6.1.3 | 0 / 6 | |
| 6.1.1 | 0 / 6 | |
| 6.1.0 | 0 / 6 | |
| 6.0.10 | 0 / 6 | |
| 6.0.9 | 0 / 6 | |
| 6.0.8 | 0 / 6 | |
| 6.0.7 | 0 / 6 | |
| 6.0.6 | 0 / 6 | |
| 6.0.5 | 0 / 6 | |
| 6.0.4 | 0 / 6 | |
| 6.0.3 | 0 / 6 | |
| 6.0.2 | 0 / 6 | |
| 6.0.1 | 0 / 6 | |
| 6.0.0 | 0 / 6 | |
| 5.1.5 | 0 / 6 | |
| 5.1.4 | 0 / 6 | |
| 5.1.3 | 0 / 6 | |
| 5.1.2 | 0 / 6 | |
| 5.1.1 | 0 / 6 | |
| 5.1.0 | 0 / 8 | |
| 5.0.102 | 0 / 8 | |
| 5.0.101 | 0 / 8 | |
| 5.0.100 | 0 / 8 | |
| 5.0.99 | 0 / 30 | |
| 5.0.98 | 0 / 7 | |
| 5.0.97 | 0 / 7 | |
| 5.0.96 | 0 / 7 | |
| 5.0.95 | 0 / 8 | |
| 5.0.94 | 0 / 9 | |
| 5.0.93 | 0 / 9 | |
| 5.0.92 | 0 / 9 | |
| 5.0.91 | 0 / 7 | |
| 5.0.90 | 0 / 4 | |
| 5.0.89 | 0 / 4 | |
| 5.0.88 | 0 / 4 | |
| 5.0.87 | 0 / 4 | |
| 5.0.86 | 0 / 4 | |
| 5.0.84 | 0 / 4 | |
| 5.0.83 | 0 / 4 | |
| 5.0.82 | 0 / 4 | |
| 5.0.81 | 0 / 4 | |
| 5.0.80 | 0 / 4 | |
| 5.0.79 | 0 / 4 | |
| 5.0.78 | 0 / 4 | |
| 5.0.76 | 0 / 4 | |
| 5.0.75 | 0 / 4 | |
| 5.0.74 | 0 / 4 | |
| 5.0.73 | 0 / 4 | |
| 5.0.72 | 0 / 4 | |
| 5.0.71 | 0 / 4 | |
| 5.0.70 | 0 / 4 | |
| 5.0.69 | 0 / 4 | |
| 5.0.67 | 0 / 4 | |
| 5.0.66 | 0 / 4 | |
| 5.0.65 | 0 / 4 | |
| 5.0.64 | 0 / 4 | |
| 5.0.63 | 0 / 4 | |
| 5.0.62 | 0 / 4 | |
| 5.0.61 | 0 / 4 | |
| 5.0.60 | 0 / 4 | |
| 5.0.59 | 0 / 4 | |
| 5.0.58 | 0 / 4 | |
| 5.0.57 | 0 / 4 | |
| 5.0.56 | 0 / 4 | |
| 5.0.55 | 0 / 4 | |
| 5.0.54 | 0 / 4 | |
| 5.0.52 | 0 / 4 | |
| 5.0.51 | 0 / 4 | |
| 5.0.50 | 0 / 4 | |
| 5.0.49 | 0 / 4 | |
| 5.0.48 | 0 / 4 | |
| 5.0.47 | 0 / 4 | |
| 5.0.46 | 0 / 4 | |
| 5.0.45 | 0 / 4 | |
| 5.0.44 | 0 / 4 | |
| 5.0.43 | 0 / 4 | |
| 5.0.42 | 0 / 4 | |
| 5.0.41 | 0 / 4 | |
| 5.0.40 | 0 / 4 | |
| 5.0.39 | 0 / 4 | |
| 5.0.38 | 0 / 4 | |
| 5.0.37 | 0 / 4 | |
| 5.0.36 | 0 / 4 | |
| 5.0.35 | 0 / 4 | |
| 5.0.34 | 0 / 4 | |
| 5.0.33 | 0 / 4 | |
| 5.0.32 | 0 / 4 | |
| 5.0.31 | 0 / 4 |
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Addition of unvetted @ariestools/sdk as a runtime dep is a supply-chain risk that generalizes to this package.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Addition of unvetted @ariestools/sdk as a runtime dep is a supply-chain risk that generalizes to this package.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Addition of unvetted @ariestools/sdk as a runtime dep is a supply-chain risk that generalizes to this package.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Addition of unvetted @ariestools/sdk as a runtime dep is a supply-chain risk that generalizes to this package.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
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: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
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: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
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: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
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-07, 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.1.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package 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.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package 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-04, 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.0.102
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package 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-04, 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.0.101
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.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.99
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.0.98
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.0.97
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.0.96
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.0.95
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.0.94
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.0.93
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.0.92
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.0.91
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.0.90
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.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.