@solar-angular/planets
This library was generated with [Nx](https://nx.dev).
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular build dependency; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect a scoped internal Angular library style, not spam/malware; consistent across all 39 versions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 20.1.2 | 3 / 0 | |
| 20.1.1 | 3 / 0 | |
| 20.1.0 | 3 / 0 | |
| 20.0.5 | 3 / 0 | |
| 20.0.4 | 3 / 0 | |
| 20.0.3 | 3 / 0 | |
| 20.0.2 | 3 / 0 | |
| 20.0.1 | 3 / 0 | |
| 20.0.0 | 3 / 0 | |
| 19.4.2 | 3 / 0 | |
| 19.4.1 | 3 / 0 | |
| 19.4.0 | 3 / 0 | |
| 19.3.4 | 3 / 0 | |
| 19.3.3 | 3 / 0 | |
| 19.3.2 | 3 / 0 | |
| 19.3.1 | 3 / 0 | |
| 19.3.0 | 3 / 0 | |
| 19.2.0 | 3 / 0 | |
| 19.1.1 | 3 / 0 |
v20.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.