@evergonlabs/tmi-evm-contracts
A set of useful contracts for TMI products
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:dist/transparentUpgradeableProxy.js | AI (source-diff): ESM variant of the same tsup bundle with inlined EVM bytecode hex strings. | ai | |
| source-diff | obfuscated-file:dist/proxyAdmin.cjs | AI (source-diff): Long lines are inlined Solidity ABI/bytecode JSON from tsup bundle, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/transparentUpgradeableProxy.cjs | AI (source-diff): Same pattern: tsup-bundled ABI/bytecode JSON, not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/proxyAdmin.js | AI (source-diff): ESM variant of the same tsup bundle with inlined EVM bytecode hex strings. | ai | |
| source-diff | encoded-string-file:dist/erc721.cjs | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/proxyAdmin.cjs | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/transparentUpgradeableProxy.cjs | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc1155.js | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc1967.js | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc20.js | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc721.js | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/proxyAdmin.js | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/transparentUpgradeableProxy.js | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc1155.cjs | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc1967.cjs | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| source-diff | encoded-string-file:dist/erc20.cjs | AI (source-diff): Long strings are EVM ABI JSON and bytecode — expected content for an EVM contracts library. | ai | |
| phantom-deps | phantom-dep:@evergonlabs/tmi-utils | AI (phantom-deps): Same-org runtime dep declared in dependencies; phantom-dep heuristic fires because it's not directly imported in this package's source. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 1 / 10 | |
| 0.7.1 | 1 / 10 | |
| 0.7.0 | 1 / 10 | |
| 0.6.7 | 1 / 10 | |
| 0.6.6 | 1 / 10 | |
| 0.6.5 | 1 / 10 | |
| 0.6.4 | 1 / 10 | |
| 0.6.3 | 1 / 10 | |
| 0.6.2 | 1 / 10 | |
| 0.6.1 | 1 / 10 | |
| 0.6.0 | 1 / 10 | |
| 0.5.2 | 1 / 10 | |
| 0.5.1 | 1 / 10 | |
| 0.5.0 | 1 / 10 | |
| 0.4.1 | 1 / 10 | |
| 0.4.0 | 1 / 10 | |
| 0.3.4 | 1 / 10 |
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
13 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
8 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
8 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
8 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
8 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
8 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.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.