chore: sync package.json with the released tags

[sairenchristianbuerano]

package.json said 0.3.1 while the latest tag was v0.4.2. Consumers resolve this action by tag, not by package.json, so the manifest had drifted without anyone noticing. Set to 0.4.3, the version about to be tagged.

Also flagged, not changed here: the description in package.json still reads "Static reliability/safety scanner", which is the phrasing retired everywhere else. It is not user-visible on the Marketplace listing (action.yml carries that), so it is left for the SEO pass rather than smuggled into a release commit.

[github-actions]

Trustabl scan

trustabl/trustabl-action · release/0.4.3 · 1 findings

Readiness goes from 100 → 100 (+0)

Readiness now   🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩   100 / 100

Projected if all findings resolved   🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩   100 / 100   +0

Findings by severity

Severity	Count
critical	0	▱▱▱▱▱▱▱▱
high	0	▱▱▱▱▱▱▱▱
medium	0	▱▱▱▱▱▱▱▱
low	0	▱▱▱▱▱▱▱▱
info	1	▰▰▰▰▰▰▰▰

Projected headroom — estimate, not a re-scan

Fix scope	Readiness	Δ
Fix critical	100 → 100	+0
+ high	100 → 100	+0
+ medium	100 → 100	+0
+ low	100 → 100	+0
+ info (all)	100 → 100	+0

Projected by re-applying trustabl's own scoring with the listed findings resolved (nothing new introduced). Treat as guidance, not a guarantee.

Metric	Value
Repository	trustabl/trustabl-action
Branch	release/0.4.3
Readiness score	100
Risk score	0
Findings	1
Max severity	info
Native exit	0
Rules version	96d33f3fbd2fbfac85f1e066ab600c0bf47e9f71

✅ Passed scanning