← Home

@ddd-ts/store-firestore

npm Repository Homepage
37
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
provenance missing-githead AI (provenance): CI/CD publish via GitHub Actions with SLSA attestation; gitHead absence is expected in this publish flow. ai
maintainer-change maintainer-added AI (maintainer-change): arthur-fontaine is the apparent monorepo owner; addition aligns with the CI/CD migration context. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with legitimate automation adoption for this monorepo. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo package with 274 versions and established publisher; metadata sparseness is structural, not suspicious. ai
npm-metadata no-description AI (npm-metadata): Monorepo package; missing description is a consistent pattern across all @ddd-ts/* packages, not a malice indicator. ai

Versions (showing 37 of 37)

Version Deps Published
0.0.49 2 / 4
0.0.48 2 / 4
0.0.47 2 / 4
0.0.46 2 / 4
0.0.45 2 / 4
0.0.44 2 / 4
0.0.43 2 / 4
0.0.42 2 / 4
0.0.41 2 / 4
0.0.40 2 / 4
0.0.39 2 / 4
0.0.38 2 / 4
0.0.37 2 / 4
0.0.36 2 / 4
0.0.35 2 / 4
0.0.34 2 / 4
0.0.33 2 / 4
0.0.32 2 / 3
0.0.31 2 / 3
0.0.30 2 / 3
0.0.29 2 / 3
0.0.28 2 / 3
0.0.27 2 / 3
0.0.26 2 / 3
0.0.25 2 / 3
0.0.24 2 / 3
0.0.23 2 / 3
0.0.22 2 / 3
0.0.21 2 / 3
0.0.20 2 / 3
0.0.19 2 / 3
0.0.18 2 / 3
0.0.17 2 / 3
0.0.16 2 / 3
0.0.15 2 / 3
0.0.14 2 / 3
0.0.13 2 / 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. Consider requesting the maintainer enable provenance via CI/CD.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.