Appearance
Code scan results
For each release, the source code of the Presently package is scanned with the tools that Salesforce uses in its AppExchange security review: Salesforce Code Analyzer and the Checkmarx source code scanner. This page lists what the scans of the current version reported, and explains why each finding is not a vulnerability.
The scans check how the package's own code reads and changes data in your org. Presently stores everything that it records in your Salesforce org, and it does not connect to any service outside Salesforce. For what Presently does with data, see Privacy and your data.
The scans of version 1.0
These results are for Presently version 1.0, which was released on November 4, 2026. Presently has not yet completed Salesforce's AppExchange security review.
| Scan | Date | Findings |
|---|---|---|
| Salesforce Code Analyzer, with the rules that Salesforce requires for the AppExchange security review | November 4, 2026 | 3 findings, about the names of three fields |
| Salesforce Graph Engine, the data flow rules of Salesforce Code Analyzer | November 4, 2026 | 1 finding, about one query that reads your org's time zone |
| Checkmarx source code scanner, run by Salesforce in its Partner Security Portal | November 4, 2026 | 3 security issues: 1 about adding people to sessions, and 2 about two queries that check Presently's rules |
The Graph Engine scan was run on the last test version before version 1.0. The Apex code that it scans is the same in version 1.0.
Every finding is explained in the sections below. Each finding names the rule that reported it, so that you can compare this page with your own scans of the package.
Three field names that contain "Key"
The ProtectSensitiveData rule (Code Analyzer, 3 results) reports custom fields whose names suggest that they store a secret, such as a password or an API key. Presently does not store passwords, tokens or API keys. Three Presently fields have "Key" in their names, and none of them stores a secret:
- The Key field of the App Setting object identifies a Presently setting. It contains the setting's name. For a setting that belongs to one user, such as a display option that the user chose, it also contains that user's ID.
- The Unique Key field of the Attendance object combines a session's ID with a contact's ID, so that a person has only one attendance record on each session.
- The Unique Key field of the Enrollment object combines an offering's ID with a contact's ID, so that a person is enrolled in each offering only once.
One query that reads your org's time zone
The AvoidDatabaseOperationInLoop rule (Graph Engine, 1 result) reports a query that can run inside a loop. The rule is about performance and Salesforce's limits on the number of queries, not about access to data. When Presently works out the date of an offering's next session, it reads your org's default time zone. Presently keeps the time zone after the first read, so the query runs at most once each time Presently handles a request, however many times the loop repeats. The scanner cannot detect that the result is kept. The query runs with the permissions of the user.
Adding enrolled people to sessions
The Sharing rule (Checkmarx, 1 result) reports a part of Presently's code that does not apply your org's sharing settings. Presently uses it for one task. When a session is created, or when a person is enrolled in an offering, Presently adds an attendance record for each enrolled person to each of the offering's sessions. When a person's enrollment is removed, it removes their unmarked attendance records from future sessions. This code runs without sharing so that the task does not fail when the user who makes the change cannot see the contact record of every enrolled person.
It is not a vulnerability, for these reasons:
- It changes only Presently's own attendance records, and it links them only to people who are already enrolled in the offering.
- It does not read any information about contacts. It sets each attendance record's link to the enrolled person's contact, and nothing else.
- It runs only after the change that started it, such as a new session or a new enrollment, has been saved with the user's own permissions. Users cannot run it directly.
Two queries that check Presently's rules
The Apex SOQL SOSL User Mode Missing query (Checkmarx, 2 results) reports two queries that do not run with the user's permissions. Presently uses them to apply its rules whatever access the user has to the fields involved. For example, a session cannot be created for an archived offering or dated after the offering's end date, and only people who can reopen a session can change the attendance on a closed session.
The queries are not a vulnerability, for these reasons:
- They read only Presently's own fields: an offering's status and end date, and whether a session is closed and which offering it belongs to.
- Only Presently's own automation uses them, when a session, an enrollment or an attendance record is saved. Their results are not shown to the user.
- The scanner found them through Presently's test classes, which call them with a record ID that is made up for the test. In your org, the IDs come from the records that the user is saving.
What the scans don't report
Presently's automation reads a few more of its own records without applying the user's permissions, where a rule must hold whoever makes the change. For example, it looks for an existing enrollment before it adds a new one, so that a person is not enrolled twice. In one place, it reads information about contacts in the same way: after two contacts are merged, it reads the ID of the contact that was kept, so that Presently's checks still recognize the person's earlier enrollments and attendance. It reads no names or other contact details this way.
If you have questions about these results, email support@turbotres.io.