← Home

@voyantjs/charters

npm Repository Homepage
4
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/charters-contracts AI (dependencies): Same-org monorepo dep pinned to matching version; consistent with coordinated voyantjs releases. ai
provenance publisher-changed AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; legitimate transition. ai
provenance missing-githead AI (provenance): GitHub Actions publishes without gitHead; expected for this CI setup. ai
license uncommon-license:FSL-1.1-Apache-2.0 AI (license): FSL-1.1-Apache-2.0 is a real license (Functional Source License); uncommon but legitimate. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is a same-version sibling @voyantjs/catalog from the same monorepo; not a third-party supply chain risk. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo package; sparse README and no keywords are expected for org-internal libs. ai

Versions (showing 4 of 219)

Version Deps Published
0.14.0 7 / 4
0.13.0 7 / 4
0.12.0 7 / 4
0.11.0 7 / 4

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

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.