@shapediver/api.platform-api-dto-v1 MIT 23 versions

@shapediver/api.platform-api-dto-v1

npm Repository Homepage

Data Transfer Object Definitions of the Platform API v1

23

Versions

MIT

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

snabelamichael_at_shapedivermatt_at_shapediverdmitry_at_shapediver

Keywords

shapediverdtoplatform

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): New publisher is a verified ShapeDiver org member with 892 approved packages; consistent org-internal handoff.	ai	2026/05/15
dependencies	unvetted-dep:chargebee-typescript	AI (dependencies): chargebee-typescript is a legitimate billing SDK; expected dependency for a platform API DTO package.	ai	2026/05/15
phantom-deps	phantom-dep:@types/q	AI (phantom-deps): @types/q is a type-only transitive dep of chargebee-typescript; not directly imported but legitimately declared.	ai	2026/05/01

Versions (showing 23 of 23)

Version	Deps	Published
2.29.12	2 / 4	2026-05-26
2.29.11	2 / 4	2026-05-19
2.29.10	2 / 4	2026-05-12
2.29.9	2 / 4	2026-04-29
2.29.8	2 / 4	2026-04-20
2.29.7	2 / 4	2026-04-20
2.29.6	2 / 4	2026-02-23
2.29.5	2 / 4	2026-02-18
2.29.4	2 / 4	2026-01-23
2.29.3	2 / 4	2026-01-15
2.29.2	2 / 4	2026-01-15
2.29.1	2 / 4	2025-12-17
2.29.0	2 / 4	2025-12-17
2.28.9	2 / 4	2025-11-13
2.28.8	2 / 3	2025-10-07
2.28.7	2 / 3	2025-09-25
2.28.6	2 / 3	2025-09-25
2.28.5	2 / 3	2025-08-22
2.28.4	2 / 3	2025-08-05
2.28.3	2 / 3	2025-07-09
2.28.2	2 / 3	2025-06-13
2.28.1	2 / 3	2025-05-07
2.28.0	2 / 3	2025-05-07

v2.29.12

1 finding

LOW No provenance attestation provenance

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

v2.29.11

1 finding

LOW No provenance attestation provenance

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

v2.29.10

1 finding

LOW No provenance attestation provenance

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

v2.29.9

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.

v2.29.8

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.

v2.29.7

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.

v2.29.6

2 findings

HIGH Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2026-02-23) provenance

This version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.29.5

2 findings

HIGH Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.29.4

2 findings

HIGH Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2026-01-23) provenance

This version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.29.3

2 findings

HIGH Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2026-01-15) provenance

This version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.29.2

2 findings

HIGH Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2026-01-15) provenance

This version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.29.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.

v2.29.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.

v2.28.9

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.

v2.28.8

1 finding

LOW No provenance attestation provenance

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

v2.28.7

1 finding

LOW No provenance attestation provenance

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

v2.28.6

1 finding

LOW No provenance attestation provenance

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

v2.28.5

1 finding

LOW No provenance attestation provenance

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

v2.28.4

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.

v2.28.3

1 finding

LOW No provenance attestation provenance

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

v2.28.2

1 finding

LOW No provenance attestation provenance

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

v2.28.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.

v2.28.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.