@valtimo/case EUPL-1.2 41 versions

@valtimo/case

npm

41

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
bogus-package	bogus-package	AI (bogus-package): Part of the established @valtimo Angular suite; missing metadata is a style issue, not a spam/malware indicator.	ai	2026/05/26
npm-metadata	no-description	AI (npm-metadata): Consistent across all @valtimo scoped packages; not a risk signal for this publisher.	ai	2026/05/26
phantom-deps	phantom-dep:tslib	AI (phantom-deps): Known implicit Angular/TypeScript runtime dep; stable false positive.	ai	2026/04/30
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Compiled Angular library; deps resolved at build time, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:@ngx-translate/http-loader	AI (phantom-deps): Compiled Angular library; deps resolved at build time, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:ngx-csv	AI (phantom-deps): Compiled Angular library; deps resolved at build time, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:muuri	AI (phantom-deps): Compiled Angular library; deps resolved at build time, not direct imports.	ai	2026/04/30

Versions (showing 41 of 41)

Version	Deps	Published
13.31.0	8 / 0	2026-06-03
13.30.0	8 / 0	2026-05-27
13.29.0	8 / 0	2026-05-20
13.28.1	8 / 0	2026-05-18
13.28.0	8 / 0	2026-05-13
13.27.0	8 / 0	2026-05-06
13.26.0	8 / 0	2026-04-29
13.24.0	8 / 0	2026-04-15
13.22.0	8 / 0	2026-04-01
13.21.0	8 / 0	2026-03-25
13.20.0	8 / 0	2026-03-18
13.19.0	8 / 0	2026-03-11
13.18.0	8 / 0	2026-03-04
13.17.1	8 / 0	2026-03-13
13.17.0	8 / 0	2026-02-25
13.16.0	8 / 0	2026-02-18
13.15.0	8 / 0	2026-02-11
13.14.0	8 / 0	2026-02-04
13.13.0	8 / 0	2026-01-28
13.12.0	8 / 0	2026-01-21
13.11.0	8 / 0	2026-01-14
13.10.0	8 / 0	2026-01-07
13.9.1	8 / 0	2025-12-24
13.9.0	8 / 0	2025-12-24
13.8.0	8 / 0	2025-12-17
13.7.0	8 / 0	2025-12-10
13.6.0	8 / 0	2025-11-26
13.5.1	8 / 0	2025-12-11
13.5.0	8 / 0	2025-11-05
13.4.1	8 / 0	2025-10-21
13.4.0	8 / 0	2025-10-20
13.3.0	8 / 0	2025-10-07
13.2.1	8 / 0	2025-09-26
13.2.0	8 / 0	2025-09-16
13.1.3	8 / 0	2025-09-12
13.1.2	8 / 0	2025-08-26
13.1.1	8 / 0	2025-08-25
13.1.0	8 / 0	2025-08-20
13.0.1	8 / 0	2025-07-22
13.0.0	8 / 0	2025-07-03
0.0.0	8 / 0	2025-12-31

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.30.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.28.0

1 finding

LOW No provenance attestation provenance

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

v13.27.0

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.24.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.

v13.21.0

1 finding

LOW No provenance attestation provenance

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

v13.20.0

1 finding

LOW No provenance attestation provenance

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

v13.19.0

1 finding

LOW No provenance attestation provenance

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

v13.18.0

1 finding

LOW No provenance attestation provenance

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

v13.17.1

1 finding

LOW No provenance attestation provenance

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

v13.17.0

1 finding

LOW No provenance attestation provenance

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

v13.16.0

1 finding

LOW No provenance attestation provenance

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

v13.15.0

1 finding

LOW No provenance attestation provenance

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

v13.14.0

1 finding

LOW No provenance attestation provenance

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

v13.13.0

1 finding

LOW No provenance attestation provenance

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

v13.12.0

1 finding

LOW No provenance attestation provenance

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

v13.11.0

1 finding

LOW No provenance attestation provenance

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

v13.10.0

1 finding

LOW No provenance attestation provenance

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

v13.9.1

1 finding

LOW No provenance attestation provenance

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

v13.9.0

1 finding

LOW No provenance attestation provenance

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

v13.8.0

1 finding

LOW No provenance attestation provenance

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

v13.7.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.6.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.5.1

1 finding

LOW No provenance attestation provenance

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

v13.5.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.4.1

1 finding

LOW No provenance attestation provenance

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

v13.4.0

1 finding

LOW No provenance attestation provenance

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

v13.3.0

1 finding

LOW No provenance attestation provenance

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

v13.2.1

1 finding

LOW No provenance attestation provenance

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

v13.2.0

1 finding

LOW No provenance attestation provenance

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

v13.1.3

1 finding

LOW No provenance attestation provenance

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

v13.1.2

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.1.1

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.1.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.0.1

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.0.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.

v0.0.0

1 finding

LOW No provenance attestation provenance

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