@nova-design-system/nova-angular-18
Nova is a design system created by Elia Group to empower creators to efficiently build solutions that people love to use.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/nova-components/esm2022/lib/providers/notification-service.component.mjs | AI (source-diff): Angular ESM2022 build output; long lines are template metadata, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/nova-components/esm2022/lib/providers/notification.service.mjs | AI (source-diff): Angular ESM2022 build output; long lines are template metadata, not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@angular/compiler | AI (phantom-deps): Framework-scoped package loaded by convention; stable for Angular libraries. | ai | |
| phantom-deps | phantom-dep:@angular/animations | AI (phantom-deps): Framework-scoped package loaded by convention; stable for Angular libraries. | ai | |
| phantom-deps | phantom-dep:zone.js | AI (phantom-deps): Angular framework dependency loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@angular/platform-browser | AI (phantom-deps): Framework-scoped package loaded by convention; stable for Angular libraries. | ai | |
| phantom-deps | phantom-dep:@angular/platform-browser-dynamic | AI (phantom-deps): Framework-scoped package loaded by convention; stable for Angular libraries. | ai | |
| phantom-deps | phantom-dep:@tanstack/angular-table | AI (phantom-deps): Config-referenced dependency; stable pattern for this design system package. | ai | |
| phantom-deps | phantom-dep:@angular/router | AI (phantom-deps): Framework-scoped package loaded by convention; stable for Angular libraries. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.31.1 | 12 / 14 | |
| 3.31.0 | 12 / 14 | |
| 3.30.0 | 12 / 14 | |
| 3.29.0 | 12 / 14 | |
| 3.28.0 | 12 / 14 | |
| 3.27.0 | 12 / 14 | |
| 3.26.0 | 12 / 14 | |
| 3.25.0 | 12 / 14 | |
| 3.24.0 | 12 / 14 | |
| 3.23.0 | 12 / 14 | |
| 3.22.0 | 12 / 14 | |
| 3.21.0 | 12 / 14 | |
| 3.20.0 | 12 / 14 | |
| 3.19.0 | 12 / 14 | |
| 3.15.0 | 11 / 14 | |
| 3.14.0 | 11 / 14 | |
| 3.13.0 | 11 / 14 | |
| 3.12.0 | 11 / 14 | |
| 3.11.0 | 11 / 14 | |
| 3.10.0 | 11 / 14 | |
| 3.9.1 | 11 / 14 | |
| 3.9.0 | 11 / 14 | |
| 3.8.0 | 11 / 14 | |
| 3.7.0 | 11 / 14 | |
| 3.6.0 | 11 / 14 | |
| 3.5.0 | 11 / 14 | |
| 3.4.0 | 11 / 14 | |
| 3.3.0 | 11 / 14 | |
| 3.2.0 | 11 / 14 | |
| 3.1.0 | 11 / 14 |
v3.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.