@gobob/sats-wagmi
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@gobob/react-query | AI (phantom-deps): Same-org scope dependency. | ai | |
| phantom-deps | phantom-dep:bip32 | AI (phantom-deps): Config-referenced Bitcoin library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:bs58check | AI (phantom-deps): Config-referenced Bitcoin encoding library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@scure/base | AI (phantom-deps): Config-referenced cryptography library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:async-retry | AI (phantom-deps): Config-referenced utility; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:sats-connect | AI (phantom-deps): Config-referenced Bitcoin wallet connector; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:bitcoinjs-lib | AI (phantom-deps): Config-referenced Bitcoin library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@gobob/bob-sdk | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query-devtools | AI (phantom-deps): Config-referenced React query devtools; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@bitcoin-js/tiny-secp256k1-asmjs | AI (phantom-deps): Config-referenced Bitcoin cryptography library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@scure/btc-signer | AI (phantom-deps): Config-referenced Bitcoin signing library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@uidotdev/usehooks | AI (phantom-deps): Config-referenced React hooks library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/providers | AI (phantom-deps): Config-referenced wallet provider; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): Config-referenced React query library; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): tsup-bundled output with readable source comments, not obfuscation. | ai | |
| phantom-deps | phantom-dep:clean-package | AI (phantom-deps): clean-package is a build tool referenced via config file, not a runtime import; stable false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.3.23 | 13 / 0 | |
| 0.3.22 | 13 / 0 | |
| 0.3.21 | 13 / 0 | |
| 0.3.20 | 13 / 0 | |
| 0.3.19 | 13 / 0 | |
| 0.3.18 | 13 / 0 | |
| 0.3.17 | 13 / 0 | |
| 0.3.16 | 13 / 0 | |
| 0.3.15 | 13 / 0 | |
| 0.3.14 | 13 / 0 | |
| 0.3.12 | 13 / 0 | |
| 0.3.11 | 13 / 0 | |
| 0.3.10 | 13 / 0 | |
| 0.3.9 | 13 / 0 | |
| 0.3.8 | 13 / 0 | |
| 0.3.7 | 13 / 0 | |
| 0.3.6 | 13 / 0 | |
| 0.3.5 | 13 / 0 | |
| 0.3.4 | 13 / 0 | |
| 0.3.3 | 13 / 0 | |
| 0.3.2 | 13 / 4 | |
| 0.2.5 | 12 / 4 | |
| 0.2.4 | 12 / 4 | |
| 0.2.3 | 14 / 4 | |
| 0.2.2 | 14 / 4 | |
| 0.2.1 | 14 / 4 | |
| 0.2.0 | 14 / 4 | |
| 0.1.0 | 13 / 4 |
v0.3.20
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2025-01-31, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.19
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2025-01-22, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.18
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2025-01-06, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.17
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-11-26, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.16
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-23, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.15
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-23, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.14
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-16, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.12
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-16, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.11
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-16, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.10
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-09, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.9
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-08, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tom-interlay) than the most recent previously approved version (ns212) on 2024-10-08, but tom-interlay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.