@nori-zk/ethereum-token-bridge
NoriTokenBridge contract
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/TimeLockController.sol/TimelockController__factory.d.ts | AI (source-diff): TypeChain-generated .d.ts with inline bytecode constant; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/TimeLockController.sol/TimelockController__factory.js | AI (source-diff): TypeChain-generated factory with EVM bytecode literal; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/MinaStateSettlement__factory.js | AI (source-diff): Long lines are ABI JSON + EVM bytecode hex strings from TypeChain codegen; not obfuscation. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/NoriTokenBridge__factory.js | AI (source-diff): Long lines are ABI JSON + EVM bytecode hex strings from TypeChain codegen; not obfuscation. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/MinaAccountValidation__factory.d.ts | AI (source-diff): Long lines are bytecode string literals in TypeChain-generated .d.ts; not obfuscation. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/NoriTokenBridge__factory.d.ts | AI (source-diff): Long lines are bytecode string literals in TypeChain-generated .d.ts; not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of multiple new TypeChain factory files with embedded ABI/bytecode. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/MinaStateSettlement__factory.d.ts | AI (source-diff): Long lines are bytecode string literals in TypeChain-generated .d.ts; not obfuscation. | ai | |
| source-diff | obfuscated-file:build/types/ethers-contracts/factories/MinaAccountValidation__factory.js | AI (source-diff): Long lines are ABI JSON + EVM bytecode hex strings from TypeChain codegen; not obfuscation. | ai | |
| phantom-deps | phantom-dep:esm-iso-logger | AI (phantom-deps): Dep is used in config files per the finding itself; not a true phantom dep for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.13 | 1 / 18 | |
| 0.0.12 | 1 / 18 | |
| 0.0.11 | 1 / 13 | |
| 0.0.10 | 0 / 17 | |
| 0.0.9 | 0 / 5 | |
| 0.0.8 | 0 / 5 | |
| 0.0.7 | 0 / 5 | |
| 0.0.6 | 0 / 5 | |
| 0.0.5 | 0 / 4 | |
| 0.0.4 | 0 / 4 | |
| 0.0.3 | 0 / 4 |
v0.0.13
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.