+0.13 Source code of Swedish e-government services has been leaked (darkwebinformer.com S:+0.11 )
232 points by tavro 2 days ago | 243 comments on HN | Mild positive Contested Low agreement (3 models) Editorial · v3.7 · 2026-03-15 23:07:47 0
Summary Digital Infrastructure & Cybersecurity Advocates
This cybersecurity news article reports on a leaked source code incident affecting Sweden's e-government platform (CGI Sverige), advocating for public awareness of critical infrastructure vulnerabilities. The content strongly exercises freedom of expression (Article 19) through accessible, transparent reporting on security breaches affecting government systems; however, it creates tensions with privacy protection (Article 12) and property rights (Article 17) by publishing full technical details without apparent redaction or limitation mechanisms.
Rights Tensions 3 pairs
Art 19 Art 12 Freedom to impart information about security breaches conflicts with privacy protection for individuals whose data flows through compromised systems; content resolves this by prioritizing transparency over privacy redaction.
Art 19 Art 17 Freedom to disclose government infrastructure details conflicts with property rights in state-owned systems; content prioritizes expression by publishing full source code without ownership limitations.
Art 19 Art 29 Freedom to express security concerns conflicts with the duty to respect limitations on rights when expression enables harm; content emphasizes disclosure without addressing Article 29 duty to consider others' rights.
Article Heatmap
Preamble: +0.19 — Preamble P Article 1: +0.24 — Freedom, Equality, Brotherhood 1 Article 2: +0.16 — Non-Discrimination 2 Article 3: ND — Life, Liberty, Security Article 3: No Data — Life, Liberty, Security 3 Article 4: ND — No Slavery Article 4: No Data — No Slavery 4 Article 5: ND — No Torture Article 5: No Data — No Torture 5 Article 6: ND — Legal Personhood Article 6: No Data — Legal Personhood 6 Article 7: ND — Equality Before Law Article 7: No Data — Equality Before Law 7 Article 8: ND — Right to Remedy Article 8: No Data — Right to Remedy 8 Article 9: ND — No Arbitrary Detention Article 9: No Data — No Arbitrary Detention 9 Article 10: ND — Fair Hearing Article 10: No Data — Fair Hearing 10 Article 11: ND — Presumption of Innocence Article 11: No Data — Presumption of Innocence 11 Article 12: -0.34 — Privacy 12 Article 13: +0.23 — Freedom of Movement 13 Article 14: ND — Asylum Article 14: No Data — Asylum 14 Article 15: ND — Nationality Article 15: No Data — Nationality 15 Article 16: ND — Marriage & Family Article 16: No Data — Marriage & Family 16 Article 17: -0.29 — Property 17 Article 18: +0.31 — Freedom of Thought 18 Article 19: +0.77 — Freedom of Expression 19 Article 20: +0.18 — Assembly & Association 20 Article 21: +0.13 — Political Participation 21 Article 22: ND — Social Security Article 22: No Data — Social Security 22 Article 23: ND — Work & Equal Pay Article 23: No Data — Work & Equal Pay 23 Article 24: ND — Rest & Leisure Article 24: No Data — Rest & Leisure 24 Article 25: +0.08 — Standard of Living 25 Article 26: +0.18 — Education 26 Article 27: +0.17 — Cultural Participation 27 Article 28: +0.28 — Social & International Order 28 Article 29: -0.18 — Duties to Community 29 Article 30: ND — No Destruction of Rights Article 30: No Data — No Destruction of Rights 30
Negative Neutral Positive No Data
Aggregates
E
+0.13
S
+0.11
Weighted Mean +0.16 Unweighted Mean +0.14
Max +0.77 Article 19 Min -0.34 Article 12
Signal 15 No Data 16
Volatility 0.26 (High)
Negative 3 Channels E: 0.6 S: 0.4
SETL +0.03 Editorial-dominant
FW Ratio 67% 52 facts · 26 inferences
Agreement Low 3 models · spread ±0.280
Evidence 24% coverage
1H 9M 5L 16 ND
Theme Radar
Foundation Security Legal Privacy & Movement Personal Expression Economic & Social Cultural Order & Duties Foundation: 0.20 (3 articles) Security: 0.00 (0 articles) Legal: 0.00 (0 articles) Privacy & Movement: -0.06 (2 articles) Personal: 0.01 (2 articles) Expression: 0.36 (3 articles) Economic & Social: 0.08 (1 articles) Cultural: 0.17 (2 articles) Order & Duties: 0.05 (2 articles)
HN Discussion 20 top-level · 30 replies
robertlagrant 2026-03-13 10:32 UTC link
The source code is the least of it! From the article:

> citizen PII databases and electronic signing documents were also collected but are being sold separately

teroshan 2026-03-13 10:41 UTC link
Does anyone know if there is the source code for the Swedish Armed Forces - Team Test [1] in the leak? It was a really fun collaborative flash-style game that got popular in my circle of friends for some reason back then.

[1] https://flashism.wordpress.com/2010/03/09/swedish-armed-forc...

rebolek 2026-03-13 10:53 UTC link
Maybe they should go open source from the start, then there's nothing to leak.

P.S.: And strangers will sometimes help you find vulnerabilities (and sometimes be very obnoxious but that's not open source's fault).

noosphr 2026-03-13 11:00 UTC link
I like paper documents for this very reason.

It's very hard to steal everyone's documents when they weight about the same as a train.

JensRantil 2026-03-13 11:02 UTC link
I am a Swedish citizen. Lived here for almost 40 years. It is a bit unclear to be what the "the Swedish e-government platform" is. Would have been great if they at least could have published which domain name the service has.
corroclaro 2026-03-13 11:04 UTC link
This keeps happening in Europe with these mega-IT suppliers repeatedly getting exposed using very bad development practices. Sweden most recently had a major breach back in 2024 when the other large IT services supplier TietoEvry had their data centres breached and claimed "not actually an issue of security".

Several government organisations / regional authorities and companies were down. Last I heard several medical journals for whole municipalities were just destroyed.

Unfortunately, the public tender process encourages awarding contracts to these giants that repeatedly fail to deliver on even basic opsec and still believe in security-by-obscurity, are suspicious of things like zero-trust, follow outdated engineering practices. Sigh.

agluszak 2026-03-13 11:28 UTC link
e-government services should be open-sources by default!
wasmitnetzen 2026-03-13 11:28 UTC link
Swedish news has some quotes from authorities that nothing of value has been leaked, and a quote from the service CGI that it only concerns test servers.[1][2]

[1]: https://www.svt.se/nyheter/inrikes/uppgift-statlig-it-inform...

[2]: https://www.cgi.com/se/sv/news/cybersakerhet/cgi-informerar-...

yaris 2026-03-13 11:37 UTC link
Knowing swedish people's mindset I'm not surprised at all by the breach. What can be mildly surprising is that no major e-gov service has expressed concerns on their websites. Only on skatteverket.se, which is Swedish Tax Service website, there is a vague note on "maintenance work" planned for coming Saturday. Maybe totally unrelated though.
WhereIsTheTruth 2026-03-13 11:40 UTC link
As long as cronyism remains the primary qualification for leadership, nothing will ever change, worse, it's only going to get worse

Accountability now, send these people to prison

elwebmaster 2026-03-13 12:19 UTC link
Anything taxpayer funded should be open source to begin with.
wayfwdmachine 2026-03-13 12:24 UTC link
Ok, some important context for non-Swedes. Anyone can get access to all Swedish (non-protected but those are a very VERY small subset) personal identification numbers by simply signing an agreement with SPAR[1] (the Swedish national people database). Identification numbers per se are not particularly useful or hard to get, they are effectively public information. Using SPAR you can also get the home (and any additional) addresses of individuals

A Swedish citizen database is... you know. fun. But not exactly hard to get hold of.

[1] https://www.statenspersonadressregister.se/master/start/engl...

bkummel 2026-03-13 13:22 UTC link
I see comments about Swedish personal identification numbers. But the article is about source code that's leaked, not a database of numbers, right? I was thinking: should government source code not be open source anyway?
FpUser 2026-03-13 13:29 UTC link
Unless they hardcode passwords and other juicy details in their source code what's all the fuzz about? It is a publicly funded thingy anyways.
GuB-42 2026-03-13 15:18 UTC link
First reaction: How come the source code is not public in the first place, accessible to every Swedish citizen? They paid for it!

But it turns out that more than the source code was leaked.

Lliora 2026-03-13 15:18 UTC link
Worked on a similar platform. The real risk isn't the code - it's the config files. Government deployments have hardcoded staging credentials, VPN endpoints, and encryption keys that don't get rotated when code leaks. Source is whatever. Those env files are the skeleton key.
vladde 2026-03-13 15:52 UTC link
CGI has a lot of consultants in both government and municipal places (i've worked at both), and some of our main tools like time reporting was built as a addon to our personnel system by consultants at CGI. half my team are consultants from CGI, 4 out of 7 people.

also: hi tavro! it's been a few years, how have you been :D

butz 2026-03-13 16:22 UTC link
Most important question: do Swedish e-government services use curl?
PeterStuer 2026-03-13 17:52 UTC link
Misleading title, as my first thought was "why is Sweden's egov not open source to begin with?".

Turns out it's about data.

dspearson 2026-03-14 11:24 UTC link
It's odd to me, as a Brit, to see that this stuff was not mostly public anyway. (looking at you https://github.com/alphagov)
simonklitj 2026-03-13 10:33 UTC link
Man, you've got to be a real low-life to sell all of that.
AdamN 2026-03-13 10:34 UTC link
Yeah the source code isn't really such a big deal aside from helping to find vulnerabilities. The PII is a real disgrace.
worldsayshi 2026-03-13 10:37 UTC link
I wonder if the focus on source code makes Swedish news slower to jump on this. I haven't seen it in domestic news yet. (Haven't looked too wide though)
jetsetman192 2026-03-13 10:41 UTC link
Encryption keys are mentioned as well.
latexr 2026-03-13 11:07 UTC link
But it’s also very easy to lose all of them in a fire or flood. Different tradeoffs.
bengale 2026-03-13 11:10 UTC link
The tender process is what they are optimised for. They are professional project bidders with a bit of outsourced software development bolted on the back.
vladms 2026-03-13 11:26 UTC link
> Unfortunately, the public tender process encourages awarding contracts to these giants that repeatedly fail to deliver on even basic opsec and still believe in security-by-obscurity

So what you think would be the solution ? From what I see (both public tender or not), I would claim that "any large IT project/company will suffer from security issues", so not sure what is the added value to single out a process (the tender) or a region (Europe) if there is no obvious alternative.

yaris 2026-03-13 11:30 UTC link
I would guess that skatteverket.se, polisen.se, kronofogden.se are among those affected by the leak.
queuep 2026-03-13 11:39 UTC link
Interesting, care to elaborate?
nunobrito 2026-03-13 11:41 UTC link
Now there is an additional reason for that.

Public money, public code.

reliablereason 2026-03-13 11:44 UTC link
Nothing in particular, based on my understanding CGI a Swedish IT consultant company was hacked, they have contracts for and are the maintainers and developers of a bunch of various government departments IT services.
ZaoLahma 2026-03-13 11:55 UTC link
Yeah. In these cases it's not like anyone is going to spin up their own instance and start competing with you.

Government / handles society-critical things code should really be public unless there are _really_ good reasons for it not to be, where those reasons are never "we're just not very good at what we're doing and we don't want anyone to find out".

bell-cot 2026-03-13 12:09 UTC link
No politician ever got elected by supporting simple, old-fashioned stuff that just worked.
einr 2026-03-13 12:26 UTC link
It's not going to be a specific service or agency with a domain name, it's going to be services that are either internal and used by employees only, or that are integrated into other systems that you may be interacting with without knowing it.
whizzter 2026-03-13 12:27 UTC link
As a Swede this is giving me shudders, the statements reeks of paper-pushers and certification-chasers that don't seem to understand fundamental risks of how how threat actors can move around once having established footholds, hopefully there's more competent people down in the trenches.
petcat 2026-03-13 12:27 UTC link
> by simply signing an agreement with SPAR

But that seems like a completely different thing than a nefarious and anonymous person or group having access to the entire database.

picafrost 2026-03-13 12:34 UTC link
I think this is good to highlight for non-Scandinavians.

Scandinavian countries are extremely open and transparent in a way that might be shocking for Americans. For example, in Norway, I can check nearly anyone's brokerage account holdings, addresses, phone numbers, etc. on public websites. I can in theory look up anyone's tax filings.

Personal identification numbers do not tend to be considered private in the same way that social security numbers in the US are.

einr 2026-03-13 12:35 UTC link
Identification numbers per se are not particularly useful or hard to get, they are effectively public information

They are absolutely trivial to get. One click on mrkoll.se.

cactusplant7374 2026-03-13 12:39 UTC link
Are we allowed to vibe code some positive changes and submit them for review?
fsflover 2026-03-13 12:44 UTC link
lysace 2026-03-13 13:09 UTC link
There is no such thing according to Peder Sjölander, IT Director at the Swedish Tax Agency:

https://www.svt.se/nyheter/inrikes/uppgift-statlig-it-inform...

– Neither our data nor our users' data has been leaked. It is a service we use for e-signatures that has been affected, but there is no data from us or our users there, says

The information that source code was leaked from a joint government e-platform is not true, according to Peder Sjölander.

– There is no such platform. I think the perpetrators in this want people to feel insecure. We feel confident that our data is safe and we have the situation under control before the tax return period opens next week.

teroshan 2026-03-13 14:05 UTC link
Similarly taxpayer funded contracts for any type of infrastructure (obviously I have digital infrastructure powered by proprietary solutions in mind) should only be awarded if interoperability is guaranteed to prevent lock-in and abuse.
ExoticPearTree 2026-03-13 14:13 UTC link
The probleme here is that what tends to happen is that the security requirements are relatively vague and once the customer has signed the acceptance, good luck.

And signing up with a big company is good way to cover your behind, because "if they with all their people and knowledge could not do it...". Basically the mantra or "Nobody was ever fired for buying Cisco".

matsemann 2026-03-13 14:16 UTC link
When I worked for the government in Norway, it slowly changed to all code being developed in the open. 3k repos here now: https://github.com/orgs/navikt/repositories

When I started it was a big security theater. Had to develop on thin clients with no external internet access, for instance. Then they got some great people in charge that modernized everything.

Only drawback is when you quit, you have to make sure to unsubscribe from everything, hehe. When quitting a private company I was just removed from the github org. Here I was as well, but I was still subscribed to lots of repos, issues, PRs,heh.

corroclaro 2026-03-13 15:33 UTC link
I'm pretty sure they did an internal analysis by 8 AM at all these places and came to the conclusion that they're OK.

Of course, they might be wrong!

sandos 2026-03-13 16:16 UTC link
I dont know nothing about this particular leak, but I have worked at Skatteverket.

Let me just say, the likelihood that CGI would have any _actual_ real personal data is close to 0%, at least on servers outside of Skatteverket. I had access to absolutely nothing even working inside. I have never worked in a more closed-down system, maybe excepting the swedish military "complex". No, actually that was less locked down in a way, at least once you were "inside" the system.

johnisgood 2026-03-13 16:59 UTC link
Ideally they should be open.
FateOfNations 2026-03-13 17:55 UTC link
The same attackers are releasing the database of personal information separately (for a fee).

That said, Sweden takes a different approach to PII, so most of that information would have already been public. You can generally just look up any resident and their ID number and other biographical details in a public directory (among other things… their tax returns are also public records).

lysace 2026-03-13 21:38 UTC link
That might be interesting but it’s also completely irrelevant since no PII was actually leaked.

Also, no source code of ”Swedish e-government services” was leaked since that is not a thing:

https://news.ycombinator.com/item?id=47363966

1718627440 2026-03-14 13:01 UTC link
I sometimes also would like that, but you might reconsider that stance when your country is in war with another one.
Editorial Channel
What the content says
+0.50
Article 19 Freedom of Expression
High Advocacy Practice
Editorial
+0.50
SETL
-0.17

Content directly exercises freedom of expression by publishing detailed reports on leaked government infrastructure source code. Publication opinion is that cybersecurity breaches merit public disclosure and discussion. Reporting contributes to public debate about government IT security.

+0.35
Article 18 Freedom of Thought
Medium Advocacy
Editorial
+0.35
SETL
+0.19

Publication of leak report demonstrates editorial exercise of freedom of thought and conscience regarding cybersecurity vulnerabilities in government systems. Reports on security incidents implicitly involve judgment about public interest in infrastructure vulnerabilities.

+0.30
Article 1 Freedom, Equality, Brotherhood
Medium Framing
Editorial
+0.30
SETL
+0.21

Content implicitly treats readers and affected populations as bearers of dignity by publishing information about infrastructure vulnerabilities that could impact public service access and security.

+0.30
Article 28 Social & International Order
Medium Framing
Editorial
+0.30
SETL
+0.12

Content advocates for an international social and political order supporting right to information. Publication of cross-border breach reporting promotes transparency norms about government infrastructure security.

+0.25
Preamble Preamble
Medium Framing
Editorial
+0.25
SETL
+0.19

Content frames disclosure of compromised government infrastructure as a matter of public information. Implicitly advocates for awareness of cybersecurity threats affecting public administration systems.

+0.25
Article 13 Freedom of Movement
Medium Advocacy
Editorial
+0.25
SETL
+0.11

Content reports on movement of sensitive information (leaked source code) across borders as part of cybersecurity incident. The publication itself exercises freedom to disseminate information about cross-border security issues.

+0.20
Article 2 Non-Discrimination
Low Framing
Editorial
+0.20
SETL
+0.14

Content reports on cybersecurity incident without discriminatory framing. No observable differentiation in reporting based on protected characteristics.

+0.20
Article 20 Assembly & Association
Low Framing
Editorial
+0.20
SETL
+0.10

Content implicitly supports freedom of peaceful assembly and association by publishing information that enables citizens to discuss and organize around cybersecurity and government transparency issues.

+0.20
Article 26 Education
Low Framing
Editorial
+0.20
SETL
+0.10

Content supports right to education by publishing information about cybersecurity threats and vulnerabilities in government systems, enabling public learning about infrastructure security.

+0.15
Article 21 Political Participation
Low Framing
Editorial
+0.15
SETL
+0.09

Content supports public participation in governance by enabling informed discourse about government IT infrastructure vulnerabilities and security practices.

+0.15
Article 27 Cultural Participation
Medium Framing Practice
Editorial
+0.15
SETL
-0.10

Content supports participation in cultural and scientific life by enabling public discourse on technological vulnerabilities and cybersecurity innovation. Publication contributes to shared cultural understanding of digital infrastructure risks.

+0.10
Article 25 Standard of Living
Low Framing
Editorial
+0.10
SETL
+0.07

Content reports on compromise of government systems that support public health, welfare, and social services access. Publication may support public awareness of vulnerabilities affecting essential service infrastructure.

-0.20
Article 29 Duties to Community
Medium Framing
Editorial
-0.20
SETL
-0.10

Content exercises expression rights without apparent consideration for limitations necessary for respecting rights of others. Full disclosure of government source code may enable violations of others' security, privacy, and property rights.

-0.35
Article 17 Property
Medium Framing
Editorial
-0.35
SETL
-0.23

Content publicly discloses leaked source code from government systems without apparent consideration for protecting proprietary systems or infrastructure owned by the state. Publication of full technical details could enable property destruction or system compromise.

-0.40
Article 12 Privacy
Medium Framing
Editorial
-0.40
SETL
-0.24

Content involves public disclosure of leaked source code from government systems. Publication may expose sensitive technical details about infrastructure used by residents, potentially enabling privacy or security violations affecting individuals' affairs and correspondence.

ND
Article 3 Life, Liberty, Security

No observable editorial content addressing right to life, liberty, or personal security.

ND
Article 4 No Slavery

No observable content addressing slavery or servitude.

ND
Article 5 No Torture

No observable content addressing torture or cruel treatment.

ND
Article 6 Legal Personhood

No observable content addressing right to recognition before law.

ND
Article 7 Equality Before Law

No observable content addressing equal protection before law.

ND
Article 8 Right to Remedy

No observable content addressing effective remedy for rights violations.

ND
Article 9 No Arbitrary Detention

No observable content addressing arbitrary arrest or detention.

ND
Article 10 Fair Hearing

No observable content addressing right to fair trial.

ND
Article 11 Presumption of Innocence

No observable content addressing presumption of innocence.

ND
Article 14 Asylum

No observable content addressing right to seek asylum.

ND
Article 15 Nationality

No observable content addressing nationality rights.

ND
Article 16 Marriage & Family

No observable content addressing marriage or family rights.

ND
Article 22 Social Security

No observable content addressing economic, social, or cultural rights.

ND
Article 23 Work & Equal Pay

No observable content addressing labor rights or employment.

ND
Article 24 Rest & Leisure

No observable content addressing rest and leisure rights.

ND
Article 30 No Destruction of Rights

No observable content addressing interpretation or implementation of UDHR rights in destructive manner.

Structural Channel
What the site does
Element Modifier Affects Note
Legal & Terms
Privacy
No privacy policy or data handling statement observable on provided page content.
Terms of Service
No terms of service observable on provided page content.
Identity & Mission
Mission
No explicit mission statement observable on provided page content.
Editorial Code
No editorial code or standards observable on provided page content.
Ownership
No ownership or publisher information observable on provided page content.
Access & Distribution
Access Model +0.10
Article 19
Content appears freely accessible without paywall, supporting open dissemination of information about cybersecurity threats.
Ad/Tracking
No ad tracking or analytics code observable in provided page content excerpt.
Accessibility +0.15
Article 19
Site includes semantic HTML, focus-visible states, color contrast variables, and screenreader utilities, enabling accessible consumption of potentially security-sensitive information.
+0.55
Article 19 Freedom of Expression
High Advocacy Practice
Structural
+0.55
Context Modifier
+0.25
SETL
-0.17

Site architecture prioritizes accessible information dissemination. Semantic HTML, screenreader utilities, and free access enable diverse users to receive and share information about cybersecurity matters. Domain accessibility modifier (+0.15) and open access model (+0.1) both support Article 19.

+0.25
Article 18 Freedom of Thought
Medium Advocacy
Structural
+0.25
Context Modifier
0.00
SETL
+0.19

Open publishing architecture enables expression of cybersecurity-related editorial positions.

+0.25
Article 28 Social & International Order
Medium Framing
Structural
+0.25
Context Modifier
0.00
SETL
+0.12

Globally accessible platform without geographic restrictions enables international dissemination of security information supporting shared understanding of infrastructure vulnerabilities.

+0.20
Article 13 Freedom of Movement
Medium Advocacy
Structural
+0.20
Context Modifier
0.00
SETL
+0.11

Site enables free information movement internationally without geographic restriction.

+0.20
Article 27 Cultural Participation
Medium Framing Practice
Structural
+0.20
Context Modifier
0.00
SETL
-0.10

Open accessible platform enables broad participation in cybersecurity and technology discussions.

+0.15
Article 1 Freedom, Equality, Brotherhood
Medium Framing
Structural
+0.15
Context Modifier
0.00
SETL
+0.21

Accessible information architecture enables equal participation in understanding matters of public governance security.

+0.15
Article 20 Assembly & Association
Low Framing
Structural
+0.15
Context Modifier
0.00
SETL
+0.10

Open publication enables information sharing necessary for collective action on cybersecurity matters.

+0.15
Article 26 Education
Low Framing
Structural
+0.15
Context Modifier
0.00
SETL
+0.10

Accessible presentation enables educational engagement with cybersecurity topics.

+0.10
Preamble Preamble
Medium Framing
Structural
+0.10
Context Modifier
0.00
SETL
+0.19

Site provides accessible free dissemination of information, supporting open knowledge exchange about critical infrastructure vulnerabilities.

+0.10
Article 2 Non-Discrimination
Low Framing
Structural
+0.10
Context Modifier
0.00
SETL
+0.14

Open access model applies to all visitors without discrimination.

+0.10
Article 21 Political Participation
Low Framing
Structural
+0.10
Context Modifier
0.00
SETL
+0.09

Open information enables participation in public debates affecting government systems.

+0.05
Article 25 Standard of Living
Low Framing
Structural
+0.05
Context Modifier
0.00
SETL
+0.07

Accessible reporting enables public understanding of threats to government service systems.

-0.15
Article 29 Duties to Community
Medium Framing
Structural
-0.15
Context Modifier
0.00
SETL
-0.10

No structural limitations restricting republication or misuse of disclosed technical information.

-0.20
Article 17 Property
Medium Framing
Structural
-0.20
Context Modifier
0.00
SETL
-0.23

No apparent controls limiting distribution or reproduction of disclosed government system code.

-0.25
Article 12 Privacy
Medium Framing
Structural
-0.25
Context Modifier
0.00
SETL
-0.24

Open dissemination of potentially sensitive government infrastructure code without access controls or redaction mechanisms.

ND
Article 3 Life, Liberty, Security

No structural impediments or supports for personal security measures.

ND
Article 4 No Slavery

Not applicable to this content type.

ND
Article 5 No Torture

Not applicable.

ND
Article 6 Legal Personhood

Not applicable to cybersecurity reporting.

ND
Article 7 Equality Before Law

Not applicable.

ND
Article 8 Right to Remedy

Not applicable.

ND
Article 9 No Arbitrary Detention

Not applicable.

ND
Article 10 Fair Hearing

Not applicable.

ND
Article 11 Presumption of Innocence

Not applicable.

ND
Article 14 Asylum

Not applicable.

ND
Article 15 Nationality

Not applicable.

ND
Article 16 Marriage & Family

Not applicable.

ND
Article 22 Social Security

Not applicable to cybersecurity incident reporting.

ND
Article 23 Work & Equal Pay

Not applicable.

ND
Article 24 Rest & Leisure

Not applicable.

ND
Article 30 No Destruction of Rights

Not applicable.

Supplementary Signals
How this content communicates, beyond directional lean. Learn more
Epistemic Quality
How well-sourced and evidence-based is this content?
0.41 medium claims
Sources
0.4
Evidence
0.3
Uncertainty
0.3
Purpose
0.6
Propaganda Flags
2 manipulative rhetoric techniques found
2 techniques detected
loaded language
Headline uses 'Full Source Code' and 'Leaked' to emphasize severity and scope of disclosure without hedging or qualification.
appeal to fear
Report on government infrastructure compromise implicitly appeals to reader concern about security vulnerabilities affecting public services.
Emotional Tone
Emotional character: positive/negative, intensity, authority
urgent
Valence
-0.3
Arousal
0.7
Dominance
0.6
Transparency
Does the content identify its author and disclose interests?
0.25
✗ Author
More signals: context, framing & audience
Solution Orientation
Does this content offer solutions or only describe problems?
0.41 problem only
Reader Agency
0.3
Stakeholder Voice
Whose perspectives are represented in this content?
0.35 2 perspectives
Speaks: institution
About: governmentindividuals
Temporal Framing
Is this content looking backward, at the present, or forward?
present immediate
Geographic Scope
What geographic area does this content cover?
national
Sweden
Complexity
How accessible is this content to a general audience?
moderate medium jargon general
Longitudinal 789 HN snapshots · 112 evals
+1 0 −1 HN
Audit Trail 132 entries
2026-03-15 23:07 eval_success Evaluated: Mild positive (0.16) - -
2026-03-15 23:07 model_divergence Cross-model spread 0.56 exceeds threshold (2 models) - -
2026-03-15 23:07 eval Evaluated by claude-haiku-4-5-20251001: +0.16 (Mild positive) 19,103 tokens +0.26
2026-03-15 23:04 eval_success Evaluated: Neutral (-0.10) - -
2026-03-15 23:04 model_divergence Cross-model spread 0.30 exceeds threshold (2 models) - -
2026-03-15 23:04 eval Evaluated by claude-haiku-4-5-20251001: -0.10 (Neutral) 20,102 tokens
2026-03-15 23:04 rater_validation_warn Validation warnings for model claude-haiku-4-5-20251001: 1W 1R - -
2026-03-15 22:42 eval_success PSQ evaluated: g-PSQ=-0.580 (3 dims) - -
2026-03-15 22:42 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 22:03 eval_success Lite evaluated: Moderate negative (-0.40) - -
2026-03-15 22:03 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) -0.06
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 22:03 rater_validation_warn Lite validation warnings for model llama-4-scout-wai: 1W 0R - -
2026-03-15 18:48 eval_success Lite evaluated: Moderate negative (-0.34) - -
2026-03-15 18:48 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) -0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 17:53 eval_success PSQ evaluated: g-PSQ=-0.580 (3 dims) - -
2026-03-15 17:53 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 17:36 eval_success Lite evaluated: Neutral (0.00) - -
2026-03-15 17:36 eval Evaluated by llama-4-scout-wai: 0.00 (Neutral) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 17:36 rater_validation_warn Lite validation warnings for model llama-4-scout-wai: 1W 0R - -
2026-03-15 16:38 eval_success PSQ evaluated: g-PSQ=-0.580 (3 dims) - -
2026-03-15 16:38 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 16:22 eval_success Lite evaluated: Neutral (0.00) - -
2026-03-15 16:22 eval Evaluated by llama-4-scout-wai: 0.00 (Neutral) +0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 16:22 rater_validation_warn Lite validation warnings for model llama-4-scout-wai: 1W 0R - -
2026-03-15 05:55 eval_success PSQ evaluated: g-PSQ=-0.580 (3 dims) - -
2026-03-15 05:55 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 05:50 eval_success Lite evaluated: Moderate negative (-0.34) - -
2026-03-15 05:50 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) -0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 05:19 eval_success PSQ evaluated: g-PSQ=-0.580 (3 dims) - -
2026-03-15 05:19 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 05:15 eval_success Lite evaluated: Neutral (0.00) - -
2026-03-15 05:15 eval Evaluated by llama-4-scout-wai: 0.00 (Neutral) +0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 05:15 rater_validation_warn Lite validation warnings for model llama-4-scout-wai: 1W 0R - -
2026-03-15 04:41 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 04:40 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) -0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-15 04:05 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-15 04:05 eval Evaluated by llama-4-scout-wai: 0.00 (Neutral) +0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 23:36 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 23:27 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 22:56 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 22:48 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 21:53 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 21:46 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 20:35 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 20:28 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 19:38 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 19:32 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 18:31 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 18:30 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 16:54 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 16:52 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 15:43 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 15:42 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 15:01 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 15:00 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 14:24 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 14:22 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 13:47 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 13:45 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 13:12 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 13:10 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 12:36 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 12:32 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 12:00 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 11:57 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 11:25 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) -0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 11:21 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 10:49 eval Evaluated by llama-4-scout-wai: 0.00 (Neutral) +0.34
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 10:45 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 10:12 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 10:06 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 09:33 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 09:25 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 08:51 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 08:42 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 08:11 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 08:00 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 07:32 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 07:20 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 06:51 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 06:36 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 06:09 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 05:56 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 05:31 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 05:18 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 04:54 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 04:36 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 04:14 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 03:59 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 03:39 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 03:20 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 02:59 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 02:43 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 02:19 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 02:04 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 01:42 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 01:22 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 01:06 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 00:47 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-14 00:40 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) +0.06
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-14 00:07 eval Evaluated by llama-3.3-70b-wai-psq: 0.00 (Neutral)
2026-03-14 00:04 eval Evaluated by llama-3.3-70b-wai: 0.00 (Neutral)
reasoning
Technical content, zero rights discussion
2026-03-13 23:59 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 23:44 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 23:08 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 22:39 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 21:48 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 21:30 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 20:47 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 20:06 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 19:20 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 18:48 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 18:07 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 17:33 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) -0.40
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 16:44 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 16:06 eval Evaluated by llama-4-scout-wai: 0.00 (Neutral) +0.40
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 15:38 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 15:30 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 14:59 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 14:53 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 14:13 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 14:08 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 13:37 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 13:32 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) -0.06
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 13:01 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 12:57 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 12:25 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 12:22 eval Evaluated by llama-4-scout-wai: -0.34 (Moderate negative) +0.06
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 11:50 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative) 0.00
2026-03-13 11:47 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative) 0.00
reasoning
Technical article about source code leak, no explicit rights discussion
2026-03-13 11:12 eval Evaluated by llama-4-scout-wai-psq: -0.58 (Moderate negative)
2026-03-13 11:10 eval Evaluated by llama-4-scout-wai: -0.40 (Moderate negative)
reasoning
Technical article about source code leak, no explicit rights discussion