@exodus/market-history
Fetches historical prices for assets
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@exodus/remote-config | AI (dependencies): First-party Exodus scoped dependency, not an unvetted third party. | ai | |
| provenance | publisher-changed | AI (provenance): CI-based publisher for Exodus monorepo package, not evidence of compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is an official @exodus first-party package. | ai | |
| provenance | no-provenance | AI (provenance): Package explicitly sets provenance:false in publishConfig; stable org-level decision across all @exodus/* packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 10.7.1 | 10 / 13 | |
| 10.7.0 | 10 / 13 | |
| 10.6.3 | 10 / 13 | |
| 10.6.2 | 10 / 13 | |
| 10.6.1 | 9 / 12 | |
| 10.6.0 | 9 / 12 | |
| 10.5.0 | 9 / 12 | |
| 10.4.0 | 9 / 12 | |
| 10.3.1 | 8 / 12 | |
| 10.3.0 | 8 / 12 | |
| 10.2.4 | 9 / 12 | |
| 10.2.3 | 9 / 12 | |
| 10.2.2 | 9 / 12 | |
| 10.2.1 | 9 / 12 | |
| 10.2.0 | 9 / 12 | |
| 10.1.3 | 9 / 12 | |
| 10.1.2 | 9 / 12 | |
| 10.1.1 | 9 / 12 | |
| 10.1.0 | 9 / 12 | |
| 10.0.1 | 9 / 12 | |
| 10.0.0 | 9 / 12 |
v10.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
2 findingsThis version was published by a different npm account (GitHub Actions) than the most recent previously approved version (joshuabot) on 2025-12-02. It has since remained available on npm for 227 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.