← Home

@myst-theme/frontmatter

npm Repository Homepage

[![@myst-theme/frontmatter on npm](https://img.shields.io/npm/v/@myst-theme/frontmatter.svg)](https://www.npmjs.com/package/@myst-theme/frontmatter) [![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/jupyter-book/myst-t

12
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ebp-botrowanc1stevejpurvesagoose77

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:myst-common AI (dependencies): Sibling monorepo package from same jupyter-book/myst-theme repo; wildcard version is standard monorepo practice. ai
dependencies unvetted-dep:myst-frontmatter AI (dependencies): Sibling monorepo package from same jupyter-book/myst-theme repo; wildcard version is standard monorepo practice. ai
bogus-package bogus-package AI (bogus-package): Scoped component package in a large monorepo; thin README and no keywords are expected for internal packages. ai
phantom-deps phantom-dep:myst-common AI (phantom-deps): myst-common is a sibling monorepo dep; phantom-dep heuristic is a false positive here. ai

Versions (showing 12 of 12)

Version Deps Published
1.3.1 9 / 1
1.3.0 9 / 1
1.2.2 9 / 1
1.2.0 9 / 1
1.1.4 9 / 1
1.1.3 9 / 1
1.1.2 9 / 1
1.1.1 9 / 1
1.1.0 9 / 1
1.0.1 9 / 1
1.0.0 9 / 1
0.18.0 9 / 1

v1.3.1

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.

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

v1.2.2

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.

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

v1.1.4

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.

v1.1.3

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.

v1.1.2

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.

v1.1.1

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.

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

v1.0.1

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.

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

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