@primate/angular
Angular for Primate
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@angular/ssr | AI (dependencies): @angular/ssr is an official Angular package; its use here is expected for an Angular framework integration. | ai | |
| phantom-deps | phantom-dep:@rcompat/fs | AI (phantom-deps): Framework-scoped utility; loaded by convention in Primate packages, not direct import. | ai | |
| phantom-deps | phantom-dep:@rcompat/build | AI (phantom-deps): Build tooling dependency; used via config/convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@rcompat/crypto | AI (phantom-deps): Framework utility; loaded by convention in Primate packages. | ai | |
| phantom-deps | phantom-dep:@rcompat/record | AI (phantom-deps): Framework utility; loaded by convention in Primate packages. | ai | |
| phantom-deps | phantom-dep:@rcompat/assert | AI (phantom-deps): Framework utility; loaded by convention in Primate packages. | ai | |
| phantom-deps | phantom-dep:@angular/ssr | AI (phantom-deps): Framework-scoped package loaded by convention in Angular SSR setups; not directly imported by design. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 8 / 1 | |
| 0.8.0 | 8 / 1 | |
| 0.7.0 | 8 / 2 | |
| 0.6.0 | 8 / 1 | |
| 0.5.0 | 13 / 0 | |
| 0.4.0 | 14 / 0 | |
| 0.3.1 | 14 / 0 |
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.