@gobob/bob-sdk
The BOB SDK helps you interact with BOB and Bitcoin, including Ordinals, BRC20, Runes, and more.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:@gobob/tokenlist | AI (npm-metadata): SHA-pinned devDep pointing to the same org's own repo; not shipped to consumers, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:global | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): ESLint framework package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@eslint/eslintrc | AI (phantom-deps): ESLint framework package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@gobob/sats-wagmi | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@bitcoinerlab/secp256k1 | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 5.6.1 | 13 / 20 | |
| 5.6.0 | 13 / 20 | |
| 5.5.5 | 13 / 20 | |
| 5.5.4 | 13 / 20 | |
| 5.5.3 | 13 / 20 | |
| 5.5.2 | 13 / 20 | |
| 5.5.1 | 13 / 20 | |
| 5.5.0 | 13 / 20 | |
| 5.4.0 | 13 / 20 | |
| 5.3.2 | 13 / 20 | |
| 5.3.1 | 12 / 20 | |
| 5.3.0 | 12 / 20 | |
| 5.2.2 | 12 / 20 | |
| 5.2.1 | 12 / 20 | |
| 5.2.0 | 12 / 20 | |
| 5.1.0 | 12 / 20 | |
| 5.0.12 | 12 / 20 | |
| 5.0.11 | 12 / 19 | |
| 5.0.10 | 12 / 19 | |
| 5.0.9 | 12 / 19 | |
| 5.0.8 | 12 / 19 | |
| 5.0.7 | 12 / 19 | |
| 5.0.6 | 12 / 19 | |
| 5.0.5 | 12 / 19 | |
| 5.0.4 | 12 / 19 | |
| 5.0.3 | 12 / 19 | |
| 5.0.2 | 12 / 19 | |
| 5.0.1 | 12 / 19 | |
| 5.0.0 | 12 / 19 | |
| 4.4.9 | 11 / 20 | |
| 4.4.8 | 11 / 20 | |
| 4.4.7 | 11 / 20 | |
| 4.4.6 | 11 / 20 | |
| 4.4.5 | 11 / 20 | |
| 4.4.4 | 11 / 20 | |
| 4.4.3 | 11 / 20 | |
| 4.4.2 | 11 / 20 | |
| 4.4.1 | 11 / 20 | |
| 4.4.0 | 11 / 20 | |
| 4.3.15 | 11 / 20 | |
| 4.3.14 | 11 / 20 | |
| 4.3.13 | 11 / 20 | |
| 4.3.12 | 11 / 18 | |
| 4.3.11 | 11 / 18 | |
| 4.3.10 | 11 / 18 |
v5.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.1
2 findingsDependency '@gobob/tokenlist' in `devDependencies` points to 'github:bob-collective/tokenlist#223e98d85d857ce316fe3a8c3814ed00ddd66556' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.