@c8y/widget-plugin
This is the Cumulocity module federation plugin. Plugins can be developed like any Cumulocity application, but can be used at runtime by other applications. Therefore, they export an Angular module which can then be imported by any other application. The
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@c8y/client | AI (phantom-deps): Same org scope; peer/framework dep pattern stable for this Angular widget package. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): Referenced in config files only; consistent with widget plugin build pattern. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a peer/transitive dep common in Angular packages; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@c8y/style | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@angular/cdk | AI (phantom-deps): Framework-scoped Angular package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:ngx-bootstrap | AI (phantom-deps): Referenced in config files; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 51 of 145)
| Version | Deps | Published |
|---|---|---|
| 1021.81.0 | 7 / 2 | |
| 1021.80.1 | 7 / 2 | |
| 1021.78.7 | 7 / 2 | |
| 1021.78.5 | 7 / 2 | |
| 1021.78.2 | 7 / 2 | |
| 1021.77.2 | 7 / 2 | |
| 1021.77.0 | 7 / 2 | |
| 1021.76.3 | 7 / 2 | |
| 1021.75.8 | 7 / 2 | |
| 1021.75.7 | 7 / 2 | |
| 1021.75.4 | 7 / 2 | |
| 1021.75.2 | 7 / 2 | |
| 1021.74.1 | 7 / 2 | |
| 1021.74.0 | 7 / 2 | |
| 1021.73.8 | 7 / 2 | |
| 1021.73.6 | 7 / 2 | |
| 1021.73.3 | 7 / 2 | |
| 1021.71.3 | 7 / 2 | |
| 1021.71.2 | 7 / 2 | |
| 1021.71.1 | 7 / 2 | |
| 1021.71.0 | 7 / 2 | |
| 1021.70.1 | 7 / 2 | |
| 1021.67.0 | 7 / 2 | |
| 1021.66.0 | 7 / 2 | |
| 1021.64.0 | 7 / 2 | |
| 1021.63.2 | 7 / 2 | |
| 1021.62.9 | 7 / 2 | |
| 1021.62.8 | 7 / 2 | |
| 1021.62.6 | 7 / 2 | |
| 1021.62.2 | 7 / 2 | |
| 1021.62.1 | 7 / 2 | |
| 1021.60.1 | 7 / 2 | |
| 1021.60.0 | 7 / 2 | |
| 1021.59.6 | 7 / 2 | |
| 1021.59.1 | 7 / 2 | |
| 1021.58.0 | 7 / 2 | |
| 1021.57.0 | 7 / 2 | |
| 1021.56.5 | 7 / 2 | |
| 1021.56.4 | 7 / 2 | |
| 1021.55.3 | 7 / 2 | |
| 1021.55.2 | 7 / 2 | |
| 1021.55.1 | 7 / 2 | |
| 1021.54.11 | 7 / 2 | |
| 1021.54.10 | 7 / 2 | |
| 1021.54.6 | 7 / 2 | |
| 1021.54.4 | 7 / 2 | |
| 1021.54.2 | 7 / 2 | |
| 1021.52.0 | 7 / 2 | |
| 1021.51.1 | 7 / 2 | |
| 1021.50.0 | 7 / 2 | |
| 1021.49.12 | 7 / 2 |
v1021.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.62.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.62.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.59.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.56.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.56.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.55.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.55.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.54.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.54.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.54.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1021.49.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.