@stratusjs/angularjs
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived monorepo package with consistent metadata; dormancy likely reflects project release cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:angular-aria | AI (phantom-deps): AngularJS module loaded by convention via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:angular-paging | AI (phantom-deps): AngularJS module loaded by convention via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:angular-animate | AI (phantom-deps): AngularJS module loaded by convention via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:angular-resource | AI (phantom-deps): AngularJS module loaded by convention via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/toastify-js | AI (phantom-deps): Type-only package loaded by framework convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:angular-messages | AI (phantom-deps): AngularJS module loaded by convention via config, not direct import; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.11.6 | 14 / 0 | |
| 0.11.5 | 14 / 0 | |
| 0.11.4 | 14 / 0 | |
| 0.11.3 | 14 / 0 | |
| 0.11.2 | 14 / 0 |
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.