@luxamm/swap-router-contracts
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv referenced in Hardhat config, not a runtime import — standard pattern for Solidity tooling. | ai | |
| phantom-deps | phantom-dep:@luxamm/v2-core | AI (phantom-deps): Same-org Solidity dependency used via Hardhat artifacts, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@luxamm/v3-core | AI (phantom-deps): Same-org Solidity dependency used via Hardhat artifacts, not direct JS import. | ai | |
| phantom-deps | phantom-dep:hardhat-watcher | AI (phantom-deps): Hardhat plugin referenced in config, not directly imported in JS — expected pattern. | ai | |
| phantom-deps | phantom-dep:@luxamm/v3-periphery | AI (phantom-deps): Same-org Solidity dependency used via Hardhat artifacts, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): OpenZeppelin Solidity contracts referenced in Hardhat config/artifacts, not direct JS import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 6 / 23 | |
| 1.3.3 | 6 / 23 | |
| 1.3.2 | 6 / 23 | |
| 1.3.1 | 1 / 0 | |
| 1.3.0 | 1 / 0 |
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.