← Home

@voyantjs/cruises

npm Repository Homepage
7
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

gabrielpxmmihaipxm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@voyantjs/cruises-contracts AI (dependencies): Same-org monorepo sibling package released in lockstep; consistent with normal voyantjs release pattern. ai
dependencies unvetted-dep:@voyantjs/catalog AI (dependencies): Sibling monorepo package following the same versioning pattern as other @voyantjs/* deps; low independent risk. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; sparse README and no keywords are typical for internal scoped packages. ai
dependencies unvetted-dep:@voyantjs/hono AI (dependencies): Same-org sibling dep at matching version; expected monorepo pattern. ai
dependencies unvetted-dep:@voyantjs/bookings AI (dependencies): Same-org sibling dep at matching version; expected monorepo pattern. ai

Versions (showing 7 of 224)

Version Deps Published
0.17.0 7 / 4
0.16.0 7 / 4
0.15.0 7 / 4
0.14.0 7 / 4
0.13.0 7 / 4
0.12.0 7 / 4
0.0.1 7 / 4

v0.17.0

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

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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

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

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

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