← Home

@ddd-ts/shape

npm Repository Homepage
41
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

arthur-fontaineaetherallyooooomi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @ddd-ts monorepo package; Levenshtein match to 'hapi' is coincidental, not a typosquat. ai
phantom-deps phantom-dep:@ddd-ts/traits AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is a stable false positive here. ai

Versions (showing 41 of 41)

Version Deps Published
0.0.49 1 / 3
0.0.48 1 / 3
0.0.47 1 / 3
0.0.46 1 / 3
0.0.45 1 / 3
0.0.44 1 / 3
0.0.43 1 / 3
0.0.42 1 / 3
0.0.41 1 / 3
0.0.40 1 / 3
0.0.39 1 / 3
0.0.38 1 / 3
0.0.37 1 / 3
0.0.36 1 / 3
0.0.35 1 / 3
0.0.34 1 / 3
0.0.33 1 / 3
0.0.32 1 / 3
0.0.31 1 / 3
0.0.30 1 / 3
0.0.29 1 / 3
0.0.28 1 / 3
0.0.27 1 / 3
0.0.26 1 / 3
0.0.25 1 / 3
0.0.24 1 / 3
0.0.23 1 / 3
0.0.22 1 / 3
0.0.21 1 / 3
0.0.20 1 / 3
0.0.19 1 / 3
0.0.18 1 / 3
0.0.17 1 / 3
0.0.16 1 / 3
0.0.15 1 / 3
0.0.14 1 / 3
0.0.13 1 / 3
0.0.12 1 / 3
0.0.11 1 / 3
0.0.10 1 / 3
0.0.9 1 / 3

v0.0.49

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.48

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.27

1 finding
LOW No provenance attestation provenance

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

v0.0.26

1 finding
LOW No provenance attestation provenance

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

v0.0.25

1 finding
LOW No provenance attestation provenance

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

v0.0.24

1 finding
LOW No provenance attestation provenance

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

v0.0.23

1 finding
LOW No provenance attestation provenance

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

v0.0.22

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

1 finding
LOW No provenance attestation provenance

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

v0.0.17

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

1 finding
LOW No provenance attestation provenance

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

v0.0.15

1 finding
LOW No provenance attestation provenance

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

v0.0.14

1 finding
LOW No provenance attestation provenance

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

v0.0.13

1 finding
LOW No provenance attestation provenance

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

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

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