← Home

domain-objects

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

uladkasach

Keywords

domain-driven-designdomaindrivendesignmodelvalidationschematypechecking

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Husky git-hooks guard; only runs when .git dir exists, safe for downstream consumers. ai
phantom-deps phantom-dep:@types/joi AI (phantom-deps): Type-only peer dep declared for consumer convenience; not directly imported. ai
phantom-deps phantom-dep:@types/yup AI (phantom-deps): Type-only peer dep declared for consumer convenience; not directly imported. ai

Versions (showing 19 of 19)

Version Deps Published
0.31.13 4 / 37
0.31.12 4 / 36
0.31.11 4 / 36
0.31.10 4 / 36
0.31.7 8 / 27
0.31.6 8 / 27
0.31.5 8 / 27
0.31.4 6 / 27
0.31.3 6 / 27
0.31.2 6 / 27
0.31.1 4 / 37
0.31.0 6 / 37
0.30.0 6 / 37
0.29.5 6 / 37
0.29.4 6 / 37
0.29.3 6 / 31
0.29.0 6 / 31
0.25.4 6 / 31
0.25.3 6 / 31

v0.31.13

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

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

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

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

1 finding
LOW No provenance attestation provenance

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

v0.31.6

1 finding
LOW No provenance attestation provenance

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

v0.31.5

1 finding
LOW No provenance attestation provenance

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

v0.31.4

1 finding
LOW No provenance attestation provenance

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

v0.31.3

1 finding
LOW No provenance attestation provenance

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

v0.31.2

1 finding
LOW No provenance attestation provenance

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

v0.31.1

1 finding
LOW No provenance attestation provenance

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

v0.31.0

1 finding
LOW No provenance attestation provenance

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

v0.30.0

1 finding
LOW No provenance attestation provenance

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

v0.29.5

1 finding
LOW No provenance attestation provenance

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

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

v0.29.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: [ -d .git ] && npm run prepare:husky || exit 0

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

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: [ -d .git ] && npm run prepare:husky || exit 0

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

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: [ -d .git ] && npm run prepare:husky || exit 0

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

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: [ -d .git ] && npm run prepare:husky || exit 0

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.