Billable Hours Timer for Freelancers – BillableCalc extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: kcolochdcbfpdidechedpkdlobjmdned
Permissions (2)
- Store local data
- Schedule tasks
Related extensions
Billable Hours — Free Time Tracker for FreelancersProductivity
BillableClock — Freelancer Time & Invoice TrackerProductivity
Billable — Time Tracker & InvoicingProductivity
Billable · Time Tracker & InvoicesProductivity
Freelance Billable — Time Tracker & Invoice MakerProductivity
Clockbill: Time Tracker for FreelancersTools
Frequently asked questions
Is Billable Hours Timer for Freelancers – BillableCalc safe to use?
Our latest automated scan rates the Chrome listing of Billable Hours Timer for Freelancers – BillableCalc at 97/100 (low risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Billable Hours Timer for Freelancers – BillableCalc require?
Billable Hours Timer for Freelancers – BillableCalc requests 2 permissions. The most significant: Store local data, Schedule tasks. See the full breakdown in the security report.
Who develops Billable Hours Timer for Freelancers – BillableCalc?
Billable Hours Timer for Freelancers – BillableCalc is published by klachev.vitali. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 0.1.1
- Current listed version
- 0.1.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.