← Home

@nysds/nys-alert

npm

The Alert component from the NYS Design System.

44
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jessegardnerplasticmindesteinborn

Keywords

new-york-statedesign-systemweb-componentslitnysalert

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@nysds/nys-icon AI (phantom-deps): Same-org web component dep; likely registered via side-effect import in bundled dist, not direct import. ai
phantom-deps phantom-dep:@nysds/nys-button AI (phantom-deps): Same-org web component dep; likely registered via side-effect import in bundled dist, not direct import. ai

Versions (showing 44 of 44)

Version Deps Published
1.19.4 2 / 3
1.19.3 2 / 3
1.19.2 2 / 3
1.19.1 2 / 3
1.19.0 2 / 3
1.18.3 2 / 3
1.18.1 2 / 3
1.18.0 2 / 3
1.17.0 2 / 3
1.16.1 2 / 3
1.16.0 2 / 3
1.15.1 2 / 3
1.15.0 2 / 3
1.14.0 2 / 3
1.13.1 2 / 3
1.13.0 2 / 3
1.12.0 2 / 3
1.11.4 2 / 3
1.11.3 2 / 3
1.11.2 2 / 3
1.11.1 2 / 3
1.11.0 2 / 3
1.10.1 2 / 3
1.10.0 2 / 3
1.9.1 2 / 3
1.9.0 2 / 3
1.8.0 2 / 3
1.7.0 2 / 3
1.6.0 2 / 5
1.5.3 2 / 5
1.5.0 0 / 5
1.4.0 0 / 5
1.3.0 0 / 5
1.2.0 0 / 5
1.1.9 0 / 5
1.1.8 0 / 5
1.1.7 0 / 5
1.1.6 0 / 5
1.1.5 0 / 5
1.1.4 0 / 5
1.1.2 0 / 5
1.1.1 2 / 3
1.1.0 2 / 3
1.0.0 2 / 3

v1.19.4

1 finding
LOW No provenance attestation provenance

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

v1.19.3

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

2 findings
MEDIUM Publisher changed: plasticmind → esteinborn (on 2025-03-24, unremoved on npm for 480d) provenance

This version was published by a different npm account (esteinborn) than the most recent previously approved version (plasticmind) on 2025-03-24. It has since remained available on npm for 480 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.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.