@rosen-bridge/bitcoin-runes-observation-extractor
Event observation data extractor for Bitcoin Runes chain
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@rosen-bridge/tokens | AI (dependencies): Internal rosen-bridge ecosystem dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/bitcoin-scanner | AI (dependencies): Internal rosen-bridge ecosystem dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/extended-typeorm | AI (dependencies): Internal rosen-bridge ecosystem dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/scanner-interfaces | AI (dependencies): Internal rosen-bridge ecosystem dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/abstract-observation-extractor | AI (dependencies): Internal rosen-bridge ecosystem dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@rosen-clients/rate-limited-axios | AI (dependencies): Internal rosen-clients ecosystem dep; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:ordiscan | AI (dependencies): Bitcoin Runes API client; expected dependency for this extractor's functionality. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 11 / 1 | |
| 3.0.0 | 11 / 1 | |
| 2.0.4 | 11 / 1 | |
| 2.0.3 | 11 / 1 | |
| 2.0.2 | 11 / 1 | |
| 2.0.1 | 11 / 1 | |
| 2.0.0 | 11 / 4 | |
| 1.1.1 | 11 / 4 | |
| 1.1.0 | 11 / 4 | |
| 1.0.3 | 11 / 4 | |
| 1.0.2 | 11 / 4 | |
| 1.0.1 | 11 / 4 | |
| 1.0.0 | 11 / 4 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.