@nysds/nys-unavheader MIT 32 versions

@nysds/nys-unavheader

npm

The Unavheader component from the NYS Design System.

32

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jessegardnerplasticmindesteinborn

Keywords

nysdsnew-york-statedesign-systemweb-componentslitnysunavheader

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/nys-unav.logo.d.ts	AI (source-diff): Long line is an inline SVG string constant in a .d.ts file, not obfuscated code.	ai	2026/05/08
phantom-deps	phantom-dep:@nysds/nys-icon	AI (phantom-deps): Same-org Lit web component; side-effect registration pattern means no direct import needed.	ai	2026/05/05
phantom-deps	phantom-dep:@nysds/nys-button	AI (phantom-deps): Same-org Lit web component; side-effect registration pattern means no direct import needed.	ai	2026/05/05
phantom-deps	phantom-dep:@nysds/nys-textinput	AI (phantom-deps): Same-org Lit web component; side-effect registration pattern means no direct import needed.	ai	2026/05/05

Versions (showing 32 of 32)

Version	Deps	Published
1.19.0	3 / 3	2026-06-09
1.18.3	3 / 3	2026-05-28
1.18.1	3 / 3	2026-05-15
1.18.0	3 / 3	2026-05-13
1.17.0	3 / 3	2026-04-30
1.16.1	3 / 3	2026-04-16
1.16.0	3 / 3	2026-04-02
1.15.1	3 / 3	2026-03-19
1.15.0	3 / 3	2026-03-06
1.14.0	3 / 3	2026-02-19
1.13.1	3 / 3	2026-02-04
1.13.0	3 / 3	2026-01-22
1.12.0	3 / 3	2025-12-11
1.11.4	3 / 3	2025-12-02
1.11.3	3 / 3	2025-11-26
1.11.2	3 / 3	2025-11-13
1.11.1	3 / 3	2025-11-04
1.11.0	3 / 3	2025-10-31
1.10.1	3 / 3	2025-10-16
1.10.0	3 / 3	2025-10-03
1.9.1	3 / 3	2025-09-18
1.9.0	3 / 3	2025-09-18
1.8.0	3 / 3	2025-09-04
1.7.0	3 / 3	2025-08-22
1.6.0	3 / 3	2025-08-07
1.5.3	3 / 3	2025-08-01
1.5.0	0 / 6	2025-07-24
1.4.0	0 / 6	2025-07-10
1.3.0	0 / 6	2025-06-26
1.2.0	0 / 6	2025-06-12
1.1.9	0 / 6	2025-05-29
1.1.8	0 / 6	2025-05-15

v1.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.18.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.0

2 findings

HIGH New obfuscated file: dist/nys-unav.logo.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.0

2 findings

HIGH New obfuscated file: dist/nys-unav.logo.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.