@operato/process
Webcomponent for business process modeling following open-wc recommendations
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:@types/file-saver | AI (phantom-deps): TypeScript type-only dep; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/sortablejs | AI (phantom-deps): TypeScript type-only dep; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@operato/property-panel | AI (phantom-deps): Same-org monorepo package; may be used transitively or via dynamic import. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 9.2.25 | 21 / 24 | |
| 9.2.23 | 21 / 24 | |
| 9.2.22 | 21 / 24 | |
| 9.2.21 | 21 / 24 | |
| 9.2.20 | 21 / 24 | |
| 9.2.19 | 21 / 24 | |
| 9.2.6 | 21 / 24 | |
| 9.2.5 | 21 / 24 | |
| 9.2.1 | 21 / 24 | |
| 9.2.0 | 21 / 24 | |
| 8.2.20 | 21 / 24 | |
| 8.2.19 | 21 / 24 | |
| 8.2.18 | 21 / 24 | |
| 8.2.17 | 21 / 24 | |
| 8.2.16 | 21 / 24 | |
| 8.2.15 | 21 / 24 | |
| 8.2.14 | 21 / 24 | |
| 8.2.13 | 21 / 24 |
v9.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.