The handleRewardsAndGetValueSent() function is called from the PhiNFT1155.sol contracts deployed. This function currently is externally exposed which means events can be spam emitted by directly calling the function. These emission is possible by passing quantity as 0 and msg.value as 0. Performing this spam is easy on low fee chains that the protocol is currently planning to deploy on.
This is also an attack idea mentioned in the README - Are there any potential issues with emitting events or executing functions when using Decent or relayer protocols? and Does the contract emit all necessary events correctly and include appropriate data?. Since we do not know how the events are going to be used by relayer protocols due to being out of scope, the issue is being submitted as QA. 
The depositRewards() function from PhiRewards contract above calls the deposit() function in the CuratorRewardsDistributor.sol contract, which would also spam emit the Deposit events. 
Consider adding a check in the handleRewardsAndGetValueSent() and deposit() function, which disallows calls if quantity = 0 or amount = 0. 
