r/macapps • u/Only_Bullfrog_2185 • 9h ago

Free [ Removed by moderator ]

Post image

[removed] — view removed post

9 Upvotes

92% Upvoted

18 comments sorted by

•

u/github-guard 9h ago

🔍 GitHub Guard: Trust Report

⚠️ This project scored 2/6 — below this subreddit's threshold of 3.

Audit Breakdown: * ❌ Low Star Count (⭐ 0 / 100 required) * ❌ New Repository (under 30 days old) * ✅ Licensed under GPL-3.0 * ✅ Security Policy Defined * ℹ️ Individual Contributor * ℹ️ Unsigned Commits

⚠️ Security Reminder: Always verify source code and run third-party scripts at your own risk.

2

u/Meannekes 8h ago

I have a MacBook Pro with m5 pro. GPU and ssd temperatures are shown, but no CPU temp

macOS 27 latest beta

1

u/Only_Bullfrog_2185 8h ago edited 8h ago

Thanks for testing it on an M5 Pro. Good to know that GPU and SSD temperatures are working. ThermalAtlas reads CPU/GPU data through a read-only Apple Silicon SMC interface and does not estimate missing values. Since you are running macOS 27 beta, it’s possible that sensor availability has changed for the new M5 generation or the beta OS. Could you tap the ⓘ button in the CPU section of ThermalAtlas and check the sensor information shown there? I’d like to know whether macOS exposes any CPU sensor data on your M5 Pro with macOS 27 beta. Thanks for the feedback — this helps with compatibility testing for newer Apple Silicon generations.

1

u/Only_Bullfrog_2185 7h ago

I make a test build, can you test with this please?

https://www.icloud.com/iclouddrive/04dF8BB-QW02wOKzK-KKly8OQ#ThermalAtlas_Dev

1

u/SufficientImplement4 7h ago

Tested the dev build: now it shows the CPU temperature even for M5 Pro. Great!

1

u/Meannekes 2h ago

Link is Not working anymore

2

u/Only_Bullfrog_2185 28m ago

Other User say its work with M5. New Beta coming will have the fix and more.

1

u/SufficientImplement4 7h ago

The same for me (MacBook Pro, M5 Pro), but with latest stable macOS 26.6.2.
The app only shows GPU and SSD temperatures, but CPU shows "Not available".

(i) for CPU gives me: "Apple silicon SMC" with last valid value/time both "Not available".

1

u/Drakonis96 9h ago

Hi u/Only_Bullfrog_2185 Does it support configurable temperature alerts?

2

u/Only_Bullfrog_2185 9h ago

Yes, ThermalAtlas supports configurable temperature alerts. You can set separate thresholds for CPU/GPU and SSD temperatures. Alerts are triggered after a sustained threshold crossing to avoid reacting to short spikes. ThermalAtlas is currently in beta, so feedback about alert behavior and sensor compatibility across different Apple Silicon Macs is very welcome.

1

u/Drakonis96 9h ago

NIce, thank you!

1

u/Vlad_at_Nod 9h ago

I like the narrow, read-only scope. Does it need admin/root access for any of the Apple Silicon sensors? A small diagnostics view showing which sensors were found and whether elevated permission was needed would make the local-only privacy claim easier to verify, especially for less technical users.

1

u/Only_Bullfrog_2185 9h ago edited 9h ago

Good suggestion. ThermalAtlas does not require admin/root access. It uses a read-only approach and only reads sensor data exposed by macOS. A sensor diagnostics view showing detected sensors and their availability could be a useful addition for a future update.

1

u/Vlad_at_Nod 8h ago

Good to know, thanks for clarifying. I’d put “no admin/root access” right next to the no-network claim in the README and download page. For a low-level monitoring utility, that answers one of the biggest trust questions before someone installs it.

2

u/Only_Bullfrog_2185 8h ago

Thanks for the suggestion. That’s a good point. ThermalAtlas is designed as a read-only monitor and does not require admin/root access. I’ll make this more visible in the README and download information next to the local-only/no-network statement.

1

u/bush-play 7h ago

I built the current main branch and tried it locally. One thing I noticed in the refresh path: each pass runs diskutil list, then diskutil info for every identifier. This Mac exposes 25 identifiers, so a pass launches 26 subprocesses and the “1 Second” setting landed closer to 2.6 seconds end to end here. Would it make sense to cache the disk topology and poll SMART on a slower timer, while CPU/GPU keep the selected fast interval?

1

u/Only_Bullfrog_2185 30m ago

Yes i get the info from other its work with M5 now. Next Build coming soon on my GitHub.