@the-situation/indexer
ETL indexer and REST/WS API for The Situation prediction markets
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@the-situation/abi | AI (phantom-deps): Same-org monorepo dep; declared for re-export without direct import is expected. | ai | |
| phantom-deps | phantom-dep:@the-situation/collateral | AI (phantom-deps): Same-org monorepo dep; declared for re-export without direct import is expected. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 11 / 2 | |
| 0.18.5 | 11 / 2 | |
| 0.18.4 | 11 / 2 | |
| 0.18.3 | 11 / 2 | |
| 0.18.2 | 11 / 2 | |
| 0.18.1 | 11 / 2 | |
| 0.18.0 | 11 / 2 | |
| 0.17.1 | 11 / 2 | |
| 0.12.0 | 11 / 2 | |
| 0.11.8 | 11 / 2 | |
| 0.11.3 | 11 / 2 | |
| 0.11.2 | 11 / 2 |
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
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.1
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.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.