@nova-design-system/nova-angular-19 SEE LICENSE IN LICENSE.MD 33 versions

@nova-design-system/nova-angular-19

npm Homepage

Nova is a design system created by Elia Group to empower creators to efficiently build solutions that people love to use.

33

Versions

SEE LICENSE IN LICENSE.MD

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

aa0006nova-design-adminevandenberghkatseleadamcooper

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:zone.js	AI (phantom-deps): zone.js is a peer dependency for Angular; loaded by convention, not direct import.	ai	2026/04/29
phantom-deps	phantom-dep:@angular/router	AI (phantom-deps): Angular framework package; loaded by convention in Angular apps.	ai	2026/04/29
phantom-deps	phantom-dep:@angular/compiler	AI (phantom-deps): Angular framework package; loaded by convention in Angular apps.	ai	2026/04/29
phantom-deps	phantom-dep:@angular/animations	AI (phantom-deps): Angular framework package; loaded by convention in Angular apps.	ai	2026/04/29
phantom-deps	phantom-dep:@tanstack/angular-table	AI (phantom-deps): Referenced in config files; loaded by convention for table integration.	ai	2026/04/29
phantom-deps	phantom-dep:@angular/platform-browser	AI (phantom-deps): Angular framework package; loaded by convention in Angular apps.	ai	2026/04/29
phantom-deps	phantom-dep:@angular/platform-browser-dynamic	AI (phantom-deps): Angular framework package; loaded by convention in Angular apps.	ai	2026/04/29

Versions (showing 33 of 33)

Version	Deps	Published
3.31.1	12 / 18	2026-05-13
3.31.0	12 / 18	2026-05-11
3.30.0	12 / 18	2026-04-27
3.29.0	12 / 18	2026-04-16
3.28.0	12 / 18	2026-03-18
3.27.0	12 / 18	2026-03-02
3.26.0	12 / 18	2026-02-24
3.25.0	12 / 18	2026-02-06
3.24.0	12 / 18	2026-01-23
3.23.0	12 / 18	2026-01-09
3.22.0	12 / 18	2025-12-08
3.21.0	12 / 18	2025-11-25
3.20.0	12 / 18	2025-11-07
3.19.0	12 / 18	2025-11-04
3.18.0	12 / 18	2025-10-24
3.17.0	12 / 18	2025-10-17
3.16.0	12 / 18	2025-10-13
3.15.0	11 / 18	2025-09-26
3.14.0	11 / 18	2025-09-19
3.13.0	11 / 18	2025-09-15
3.12.0	11 / 18	2025-08-29
3.11.0	11 / 18	2025-08-19
3.10.0	11 / 18	2025-08-08
3.9.1	11 / 18	2025-07-23
3.9.0	11 / 18	2025-07-18
3.8.0	11 / 18	2025-07-04
3.7.0	11 / 18	2025-06-27
3.6.0	11 / 18	2025-06-19
3.5.0	11 / 14	2025-06-16
3.4.0	11 / 14	2025-06-10
3.3.0	11 / 14	2025-05-28
3.2.0	11 / 14	2025-05-20
3.1.0	11 / 14	2025-04-28

v3.31.1

1 finding

LOW No provenance attestation provenance

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

v3.31.0

1 finding

LOW No provenance attestation provenance

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

v3.29.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.

v3.28.0

1 finding

LOW No provenance attestation provenance

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

v3.27.0

1 finding

LOW No provenance attestation provenance

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

v3.26.0

1 finding

LOW No provenance attestation provenance

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

v3.25.0

1 finding

LOW No provenance attestation provenance

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

v3.24.0

1 finding

LOW No provenance attestation provenance

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

v3.23.0

1 finding

LOW No provenance attestation provenance

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

v3.22.0

1 finding

LOW No provenance attestation provenance

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

v3.21.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.

v3.20.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.

v3.19.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.

v3.18.0

1 finding

LOW No provenance attestation provenance

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

v3.17.0

1 finding

LOW No provenance attestation provenance

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

v3.16.0

1 finding

LOW No provenance attestation provenance

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

v3.15.0

1 finding

LOW No provenance attestation provenance

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

v3.14.0

1 finding

LOW No provenance attestation provenance

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

v3.13.0

1 finding

LOW No provenance attestation provenance

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

v3.12.0

1 finding

LOW No provenance attestation provenance

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

v3.11.0

1 finding

LOW No provenance attestation provenance

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

v3.10.0

1 finding

LOW No provenance attestation provenance

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

v3.9.1

1 finding

LOW No provenance attestation provenance

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

v3.9.0

1 finding

LOW No provenance attestation provenance

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

v3.8.0

1 finding

LOW No provenance attestation provenance

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

v3.7.0

1 finding

LOW No provenance attestation provenance

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

v3.6.0

1 finding

LOW No provenance attestation provenance

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

v3.5.0

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.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.

v3.1.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.