← Home

@jvs-milkdown/utils

58
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jvs-milkdown

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Consistent @jvs-milkdown scoped fork; missing gitHead across versions is a CI config issue, not a malware indicator. ai
bogus-package bogus-package AI (bogus-package): Part of a coherent scoped package family (@jvs-milkdown/*); sparse README is typical for utility sub-packages. ai
provenance no-provenance AI (provenance): No provenance is common; no other risk signals elevate this. ai

Versions (showing 58 of 58)

Version Deps Published
1.2.50 6 / 0
1.2.49 6 / 0
1.2.48 6 / 0
1.2.47 6 / 0
1.2.46 6 / 0
1.2.45 6 / 0
1.2.44 6 / 0
1.2.43 6 / 0
1.2.42 6 / 0
1.2.40 6 / 0
1.2.38 6 / 0
1.2.37 6 / 0
1.2.36 6 / 0
1.2.35 6 / 0
1.2.34 6 / 0
1.2.33 6 / 0
1.2.32 6 / 0
1.2.31 6 / 0
1.2.30 6 / 0
1.2.29 6 / 0
1.2.28 6 / 0
1.2.27 6 / 0
1.2.26 6 / 0
1.2.25 6 / 0
1.2.24 6 / 0
1.2.23 6 / 0
1.2.22 6 / 0
1.2.21 6 / 0
1.2.20 6 / 0
1.2.18 6 / 0
1.2.17 6 / 0
1.2.16 6 / 0
1.2.15 6 / 0
1.2.14 6 / 0
1.2.13 6 / 0
1.2.12 6 / 0
1.2.11 6 / 0
1.2.10 6 / 0
1.2.9 6 / 0
1.2.8 6 / 0
1.2.7 6 / 0
1.2.5 6 / 0
1.2.4 6 / 0
1.2.3 6 / 0
1.2.2 6 / 0
1.2.1 6 / 0
1.2.0 6 / 0
1.1.9 6 / 0
1.1.8 6 / 0
1.1.7 6 / 0
1.1.6 6 / 0
1.1.5 6 / 0
1.1.4 6 / 0
1.1.3 6 / 0
1.1.2 6 / 0
1.1.1 6 / 0
1.1.0 6 / 0
1.0.0 6 / 0

v1.2.50

1 finding
INFO No provenance attestation provenance

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

v1.2.49

1 finding
INFO No provenance attestation provenance

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

v1.2.48

1 finding
INFO No provenance attestation provenance

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

v1.2.47

1 finding
INFO No provenance attestation provenance

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

v1.2.46

1 finding
INFO No provenance attestation provenance

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

v1.2.45

1 finding
INFO No provenance attestation provenance

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

v1.2.44

1 finding
INFO No provenance attestation provenance

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

v1.2.43

1 finding
INFO No provenance attestation provenance

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

v1.2.42

1 finding
INFO No provenance attestation provenance

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

v1.2.40

1 finding
INFO No provenance attestation provenance

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

v1.2.38

1 finding
INFO No provenance attestation provenance

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

v1.2.37

1 finding
INFO No provenance attestation provenance

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

v1.2.36

1 finding
INFO No provenance attestation provenance

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

v1.2.35

1 finding
INFO No provenance attestation provenance

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

v1.2.34

1 finding
INFO No provenance attestation provenance

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

v1.2.33

1 finding
INFO No provenance attestation provenance

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

v1.2.32

1 finding
INFO No provenance attestation provenance

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

v1.2.31

1 finding
INFO No provenance attestation provenance

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

v1.2.30

1 finding
INFO No provenance attestation provenance

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

v1.2.29

1 finding
INFO No provenance attestation provenance

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

v1.2.0

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jvs-milkdown.