<secure-input>
A drop-in replacement for <input> that moves security enforcement inside a closed Shadow DOM. Scripts, extensions, and devtools cannot read the field value or reach its internal state. Every interaction is measured — focus timing, typing velocity, paste events — and dispatched as a secure-audit event on your server.
<script type="module"
src="/components/secure-input/secure-input.js">
</script>Configurations
<secure-input
label="Access Token"
name="token"
security-tier="critical">
</secure-input><secure-input
label="Email Address"
name="email"
type="email"
security-tier="sensitive"
required>
</secure-input>autocomplete="new-password" set automatically. Paste events are recorded in the audit log. The plaintext never touches the light DOM.<secure-input
label="Password"
name="password"
type="password"
security-tier="critical"
required>
</secure-input><secure-input
label="Display Name"
name="display_name"
security-tier="public">
</secure-input><form> constraint validation and checkValidity().<secure-input
label="Company Name"
name="company"
required
security-tier="public">
</secure-input>input.maxLength from outside. Violation is recorded in the audit log.<secure-input
label="Username"
name="username"
minlength="3"
maxlength="20"
security-tier="public">
</secure-input>Security Features
These are client-side defences. Server-side validation is always the security boundary — these reduce the attack surface and produce a complete interaction record for your server to act on.
secure-threat-detected on every input eventEvery keystroke is scanned against 8 patterns. Only the first match per event is reported. The raw field value is never included in the event detail.
el.addEventListener('secure-threat-detected', e => {
const { fieldName, threatType,
patternId, tier, timestamp } = e.detail;
// threatType: 'injection'
// patternId: e.g. 'script-tag', 'js-protocol'
// raw value intentionally absent
});<script tagsjavascript: URIsonclick=, onload=<img>, <svg>, <iframe>, etc.expression() CSSvbscript: URIsdata:text/html payloads{{...}} template injection probesthreat-feedback attributeAdd threat-feedback to show an amber inline warning directly below the field when a pattern matches. The message identifies the blocked pattern and security tier. It clears automatically when the input is clean. The underlying secure-threat-detected event fires regardless — silent detection is always on.
<!-- Inline feedback enabled -->
<secure-input
type="text"
label="Username"
name="username"
security-tier="authenticated"
threat-feedback>
</secure-input>
<!-- Silent detection only (e.g. code editor) -->
<secure-input
type="text"
label="Code"
name="code">
</secure-input><script>alert(1)</script>| Feature | Public | Authenticated | Sensitive | Critical |
|---|---|---|---|---|
| Closed Shadow DOM isolation | Yes | Yes | Yes | Yes |
| XSS sanitization | Yes | Yes | Yes | Yes |
| Real-time injection detection | Yes | Yes | Yes | Yes |
Inline threat feedback (threat-feedback) | Opt-in | Opt-in | Opt-in | Opt-in |
| Progressive enhancement (no-JS fallback) | Yes | Yes | Yes | Yes |
| Behavioral telemetry | - | Yes | Yes | Yes |
| Audit logging | - | Yes | Yes | Yes |
| Autocomplete disabled | - | - | Yes | Yes |
| Rate limiting | - | - | Yes | Yes |
Theming
Secure-UI uses CSS custom properties. Override at :root, per-component, or per-instance.
| Variable | Default | Description |
|---|---|---|
| --secure-ui-input-height | 2.5rem | Input element height |
| --secure-ui-input-padding-x | 0.75rem | Horizontal padding |
| --secure-ui-input-font-size | 0.9375rem | Font size inside input |
| --secure-ui-input-border-radius | 6px | Corner radius |
| --secure-ui-input-bg | var(--secure-ui-color-bg-primary) | Input background color |
| --secure-ui-input-border-color | var(--secure-ui-color-border) | Default border color |
| --secure-ui-input-border-color-focus | var(--secure-ui-color-primary) | Border color on focus |
| --secure-ui-input-text-color | var(--secure-ui-color-text-primary) | Input text color |
.my-form secure-input {
--secure-ui-input-border-radius: 2px;
--secure-ui-input-border-color: #6366f1;
--secure-ui-input-border-color-focus: #818cf8;
--secure-ui-input-height: 3rem;
}Framework Examples
Web Components work natively in all frameworks. No wrappers, no adapters.
<!DOCTYPE html>
<html>
<head>
<script type="module"
src="/components/secure-input/secure-input.js">
</script>
</head>
<body>
<secure-input
type="email"
label="Email"
name="email"
security-tier="sensitive"
required>
</secure-input>
</body>
</html>import { useEffect } from 'react';
// Extend JSX types for custom element
declare global {
namespace JSX {
interface IntrinsicElements {
'secure-input': React.DetailedHTMLProps<
React.HTMLAttributes<HTMLElement> & {
label?: string;
name?: string;
type?: string;
'security-tier'?: string;
required?: boolean;
},
HTMLElement
>;
}
}
}
export function EmailField() {
useEffect(() => {
import('/components/secure-input/secure-input.js');
}, []);
return (
<secure-input
type="email"
label="Email"
name="email"
security-tier="sensitive"
required
/>
);
}<template>
<secure-input
type="email"
label="Email"
:name="fieldName"
security-tier="sensitive"
required
/>
</template>
<script setup>
import { onMounted } from 'vue';
const fieldName = 'email';
onMounted(() => {
import('/components/secure-input/secure-input.js');
});
</script>import { Component, CUSTOM_ELEMENTS_SCHEMA, OnInit } from '@angular/core';
@Component({
selector: 'app-email-field',
template: `
<secure-input
type="email"
label="Email"
name="email"
security-tier="sensitive"
required>
</secure-input>
`,
schemas: [CUSTOM_ELEMENTS_SCHEMA],
})
export class EmailFieldComponent implements OnInit {
ngOnInit() {
import('/components/secure-input/secure-input.js');
}
}<script>
import { onMount } from 'svelte';
onMount(() => {
import('/components/secure-input/secure-input.js');
});
</script>
<secure-input
type="email"
label="Email"
name="email"
security-tier="sensitive"
required>
</secure-input>templ EmailField(name string, required bool) {
<secure-input
type="email"
label="Email Address"
name={ name }
security-tier="sensitive"
if required {
required
}
></secure-input>
}