ovaltine | The chocolatey treat which makes your Cocoa UI code clean | iOS library

No.

Access-Modifiers are used to restrict access of members to callers of your class. This is useful to enforce encapsulation, one of the primary goals introduced with object oriented programming OOP ( hiding implementation details, etc.).

When you compile your code to a DLL, it is translated to Intermediate Language (IL) in an Assembly (which technically has little to do with classic unmanaged(Win32 Dynamic Link Libraries), which at runtime gets compiled to machine code on the target machine (via Just-In-Time Compiler, JIT).

The IL however, can easily be "reverse-engineered" using tools like ILSpy, so literally everyone with access to your assembly can "read" the secret.

(To go further, even private readonly fields can be modified from outside the class using reflection, but that is a topic on it´s own).

I played around with your code and found that removing default from the user-status.js module fixed the problem. I suspect the reason has something to do with how Aurelia utilizes module-loaders (System.js, webpack, ...) when importing modules. Unfortunately I don't know enough about the internals of Aurelia to give a more in-depth answer.