@rosen-bridge/bitcoin-observation-extractor
Event observation data extractor for Bitcoin 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 sibling package from the same rosen-bridge org; expected dependency. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/bitcoin-scanner | AI (dependencies): Internal sibling package from the same rosen-bridge org; expected dependency. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/extended-typeorm | AI (dependencies): Internal sibling package from the same rosen-bridge org; expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Rosen-bridge packages consistently lack provenance; stable false positive for this publisher. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 6 / 0 | |
| 8.0.0 | 6 / 0 | |
| 7.0.4 | 6 / 0 | |
| 7.0.3 | 6 / 0 | |
| 7.0.2 | 6 / 0 | |
| 7.0.1 | 6 / 0 | |
| 7.0.0 | 6 / 0 | |
| 6.4.1 | 6 / 0 | |
| 6.4.0 | 6 / 0 |
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.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.