@valtimo/process-management EUPL-1.2 39 versions

@valtimo/process-management

npm

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.2.14.

39

Versions

EUPL-1.2

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

devops-ritense

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@bpmn-io/properties-panel	AI (dependencies): @bpmn-io/properties-panel is a legitimate bpmn-io ecosystem library; stable dependency for this process-management package.	ai	2026/05/30
publish-pattern	new-deps-added	AI (publish-pattern): Added deps are established bpmn-io libraries appropriate for a process-management package.	ai	2026/05/30
phantom-deps	phantom-dep:@bpmn-io/properties-panel	AI (phantom-deps): Likely used indirectly via bpmn-js-properties-panel; stable false positive for this package.	ai	2026/05/26
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is explicitly declared in dependencies; phantom-dep is a false positive for this Angular library package.	ai	2026/04/30

Versions (showing 39 of 39)

Version	Deps	Published
13.31.0	6 / 0	2026-06-03
13.29.0	6 / 0	2026-05-20
13.28.1	6 / 0	2026-05-18
13.26.0	6 / 0	2026-04-29
13.25.0	6 / 0	2026-04-22
13.22.0	6 / 0	2026-04-01
12.36.0	3 / 0	2026-05-20
12.35.0	3 / 0	2026-05-13
12.34.0	3 / 0	2026-05-06
12.33.1	3 / 0	2026-04-30
12.33.0	3 / 0	2026-04-29
12.32.0	3 / 0	2026-04-23
12.31.0	3 / 0	2026-04-15
12.30.0	3 / 0	2026-04-08
12.29.0	3 / 0	2026-04-01
12.28.1	3 / 0	2026-03-25
12.28.0	3 / 0	2026-03-18
12.27.0	3 / 0	2026-03-04
12.26.0	3 / 0	2026-02-25
12.25.0	3 / 0	2026-02-18
12.24.0	3 / 0	2026-01-28
12.23.1	3 / 0	2026-01-19
12.23.0	3 / 0	2026-01-14
12.22.0	3 / 0	2026-01-07
12.21.1	3 / 0	2025-12-24
12.21.0	3 / 0	2025-12-03
12.20.1	3 / 0	2025-11-28
12.20.0	3 / 0	2025-11-12
12.19.0	3 / 0	2025-10-28
12.18.0	3 / 0	2025-10-09
12.17.1	3 / 0	2025-09-25
12.17.0	3 / 0	2025-09-16
12.16.1	3 / 0	2025-08-29
12.16.0	3 / 0	2025-08-28
12.15.1	3 / 0	2025-08-01
12.15.0	3 / 0	2025-07-31
12.14.1	3 / 0	2025-06-24
12.14.0	3 / 0	2025-06-22
12.12.0	3 / 0	2025-05-02

v13.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.28.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v13.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v13.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.36.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.35.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.34.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.33.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.33.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.32.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.30.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.28.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.24.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.23.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.21.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.20.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.