← Home

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

npm Repository Homepage

Data Transfer Object Definitions of the Platform API v1

47
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

snabelamichael_at_shapedivermatt_at_shapediverdmitry_at_shapediver

Keywords

shapediverdtoplatform

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): New publisher is a verified ShapeDiver org member with 892 approved packages; consistent org-internal handoff. ai
dependencies unvetted-dep:chargebee-typescript AI (dependencies): chargebee-typescript is a legitimate billing SDK; expected dependency for a platform API DTO package. ai
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

Versions (showing 47 of 47)

Version Deps Published
2.29.19 2 / 4
2.29.18 2 / 4
2.29.17 2 / 4
2.29.16 2 / 4
2.29.15 2 / 4
2.29.14 2 / 4
2.29.13 2 / 4
2.29.12 2 / 4
2.29.11 2 / 4
2.29.10 2 / 4
2.29.9 2 / 4
2.29.8 2 / 4
2.29.7 2 / 4
2.29.6 2 / 4
2.29.5 2 / 4
2.29.4 2 / 4
2.29.3 2 / 4
2.29.2 2 / 4
2.29.1 2 / 4
2.29.0 2 / 4
2.28.9 2 / 4
2.28.8 2 / 3
2.28.7 2 / 3
2.28.6 2 / 3
2.28.5 2 / 3
2.28.4 2 / 3
2.28.3 2 / 3
2.28.2 2 / 3
2.28.1 2 / 3
2.28.0 2 / 3
2.27.11 2 / 3
2.27.10 2 / 3
2.27.9 2 / 3
2.27.8 2 / 3
2.27.7 2 / 3
2.27.6 2 / 3
2.27.5 2 / 3
2.27.4 2 / 3
2.27.3 2 / 3
2.27.2 2 / 3
2.27.1 2 / 3
2.27.0 2 / 3
2.26.1 2 / 3
2.26.0 2 / 3
2.25.0 2 / 3
2.24.0 2 / 3
2.23.1 2 / 3

v2.29.19

1 finding
LOW No provenance attestation provenance

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

v2.29.18

1 finding
LOW No provenance attestation provenance

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

v2.29.17

1 finding
LOW No provenance attestation provenance

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

v2.27.11

1 finding
LOW No provenance attestation provenance

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

v2.27.10

1 finding
LOW No provenance attestation provenance

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

v2.27.9

1 finding
LOW No provenance attestation provenance

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

v2.27.8

1 finding
LOW No provenance attestation provenance

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

v2.27.7

1 finding
LOW No provenance attestation provenance

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

v2.27.6

1 finding
LOW No provenance attestation provenance

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

v2.27.5

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

1 finding
LOW No provenance attestation provenance

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

v2.27.3

1 finding
LOW No provenance attestation provenance

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

v2.27.2

1 finding
LOW No provenance attestation provenance

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

v2.27.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2024-08-30, known maintainer) provenance

This version was published by a different npm account (dmitry_at_shapediver) than the most recent previously approved version (matt_at_shapediver) on 2024-08-30, but dmitry_at_shapediver is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.27.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dmitry_at_shapediver → matt_at_shapediver (on 2024-07-24, known maintainer) provenance

This version was published by a different npm account (matt_at_shapediver) than the most recent previously approved version (dmitry_at_shapediver) on 2024-07-24, but matt_at_shapediver is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.26.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: matt_at_shapediver → dmitry_at_shapediver (on 2024-06-19, known maintainer) provenance

This version was published by a different npm account (dmitry_at_shapediver) than the most recent previously approved version (matt_at_shapediver) on 2024-06-19, but dmitry_at_shapediver is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.26.0

1 finding
LOW No provenance attestation provenance

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

v2.25.0

1 finding
LOW No provenance attestation provenance

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

v2.24.0

1 finding
LOW No provenance attestation provenance

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

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