I have developed package Bof Per Man and pushed it into AppExchange.
It has separate tabs to mass add or mass remove permissions from selected profiles and permission sets to selected objects, fields and tabs.
In Locker Service (LS), they use an ObservableMembrane with a readOnlyMembrane within it that protects cached values. This membrane immediately rejects any writes to the protected object. If you attempt to write to an existing property, you get an error that reads Cannot assign to read only property 'x' on object, while if you attempt to write a non-existent ...
So having spoken to our Salesforce Technical Evangelist we were basically told not to worry about it. From my basic understanding after the meeting: when you do your first security review (and pass) there is a flag set against the package to say it has successfully passed. This flag is never unset. What happens is that Salesforce decides to review the ...
My client has opened a case in Salesforce support.
Meanwhile I have some conjectures.
There were no changes between the beta version 33 and released version 34 and there were only LWC changes between version 32 and version 33.
Since Checkmarx scanner verifies only Apex, this might be the reason for the package version not showing up in the checkmarx scanner, ...
Fields and objects each have their own security. You are expected to check every object and field, e.g. MyCustomObject__c.field1__c.getDescribe().isCreateable(). You can simplify these checks with Security.stripInaccessible.
Based on docs Account team access is only visible if the user having below access,
Edit access on account record.
User is an Account owner or User need to available in above/parent Role of the Account owner's role in Role hierarchy.
Please let me know if it helps.