@exodus/atoms
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 |
|---|---|---|---|---|
| license | uncommon-license:UNLICENSED | AI (license): Proprietary package; UNLICENSED is intentional and consistent across all versions. | ai | |
| dependencies | unvetted-dep:proxy-freeze | AI (dependencies): Small utility dep from a stable package; no malware indicators. | ai | |
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): Well-known tiny assertion library; no risk. | ai | |
| dependencies | unvetted-dep:@exodus/storage-interface | AI (dependencies): First-party Exodus dep consistent with the package's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; intentional for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 10.3.4 | 9 / 9 | |
| 10.3.3 | 9 / 9 | |
| 10.3.2 | 9 / 9 | |
| 10.3.1 | 9 / 9 | |
| 10.3.0 | 9 / 9 | |
| 10.2.2 | 9 / 9 | |
| 10.2.1 | 9 / 9 | |
| 10.2.0 | 9 / 9 | |
| 10.1.0 | 9 / 9 | |
| 10.0.0 | 9 / 9 |
v10.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.
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.