@rosen-bridge/rosen-extractor
this project contains methods to get rosen data from blockchain
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has 11 approved packages with no provenance issues. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/address-codec | AI (dependencies): First-party @rosen-bridge org dependency; consistent with the rest of the package's dependency graph. | ai | |
| dependencies | unvetted-dep:ergo-lib-wasm-nodejs | AI (dependencies): Official Ergo blockchain WASM binding; expected for Ergo chain support. | ai | |
| dependencies | unvetted-dep:@cardano-ogmios/schema | AI (dependencies): Official Cardano Ogmios schema dep; expected for Cardano chain support. | ai | |
| dependencies | unvetted-dep:@blockfrost/openapi | AI (dependencies): Legitimate Blockfrost API schema dep; consistent with blockchain extractor purpose. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/abstract-logger | AI (dependencies): First-party @rosen-bridge utility; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/address-manager | AI (dependencies): First-party @rosen-bridge utility; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/json-bigint | AI (dependencies): First-party @rosen-bridge utility; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@rosen-bridge/tokens | AI (dependencies): First-party @rosen-bridge ecosystem dep; stable pattern across versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 12.0.2 | 12 / 2 | |
| 12.0.1 | 12 / 2 | |
| 12.0.0 | 12 / 2 | |
| 11.2.1 | 12 / 4 | |
| 11.2.0 | 12 / 4 | |
| 11.1.2 | 12 / 4 | |
| 11.1.1 | 12 / 4 | |
| 11.1.0 | 12 / 4 |
v12.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.