@abp/ng.theme.shared
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Bootstrap referenced in config/styles, not directly imported in JS; expected pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Peer/config-level dep for Bootstrap; not directly imported in JS by design. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-free | AI (phantom-deps): Icon font referenced in config/styles; expected pattern for theme packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 10.4.1 | 8 / 0 | |
| 10.4.0 | 8 / 0 | |
| 10.3.0 | 8 / 0 | |
| 10.2.1 | 8 / 0 | |
| 10.2.0 | 8 / 0 | |
| 10.1.1 | 8 / 0 | |
| 10.1.0 | 8 / 0 | |
| 10.0.3 | 8 / 0 | |
| 10.0.2 | 8 / 0 | |
| 10.0.1 | 8 / 0 | |
| 10.0.0 | 8 / 0 | |
| 9.3.7 | 8 / 0 |
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.