← Home

monogon

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

maybebot

Keywords

blockcodedevelopereditorhighlightingmonogonsnippetsyntaxtooling

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing; SLSA provenance attestation confirms integrity and repo ownership unchanged. ai

Versions (showing 22 of 22)

Version Deps Published
0.3.8 0 / 15
0.3.7 0 / 15
0.3.6 0 / 15
0.3.5 0 / 15
0.3.4 0 / 14
0.3.3 0 / 14
0.3.2 0 / 14
0.3.1 0 / 14
0.3.0 0 / 12
0.2.6 0 / 9
0.2.5 0 / 9
0.2.4 0 / 9
0.2.3 0 / 9
0.2.2 0 / 8
0.2.1 0 / 8
0.2.0 0 / 8
0.1.4 0 / 8
0.1.3 0 / 8
0.1.2 0 / 8
0.1.1 0 / 8
0.1.0 0 / 8
0.0.1 0 / 7

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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