@duetds/marked
This package includes Duet Markdown utilities and related tools.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher name matches company in package.json author field; no behavioral change in diff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Stale publisher change with 498d clean history and clean diff; not a takeover pattern. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stale publish inconsistent with account takeover; publisher has clean track record. | ai |
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 3.1.64 | 0 / 11 | |
| 3.1.63 | 0 / 11 | |
| 3.1.62 | 0 / 11 | |
| 3.1.61 | 0 / 11 | |
| 3.1.60 | 0 / 11 | |
| 3.1.59 | 0 / 11 | |
| 3.1.58 | 0 / 11 | |
| 3.1.57 | 0 / 11 | |
| 3.1.56 | 0 / 11 | |
| 3.1.55 | 0 / 11 | |
| 3.1.54 | 0 / 11 | |
| 3.1.53 | 0 / 11 | |
| 3.1.52 | 0 / 11 | |
| 3.1.51 | 0 / 11 | |
| 3.1.50 | 0 / 11 | |
| 3.1.49 | 0 / 11 | |
| 3.1.48 | 0 / 11 | |
| 3.1.47 | 0 / 11 | |
| 3.1.46 | 0 / 11 | |
| 3.1.45 | 0 / 11 | |
| 3.1.44 | 0 / 11 | |
| 3.1.43 | 0 / 11 | |
| 3.1.42 | 0 / 11 | |
| 3.1.41 | 0 / 11 | |
| 3.1.40 | 0 / 11 | |
| 3.1.39 | 0 / 11 | |
| 3.1.38 | 0 / 11 | |
| 3.1.37 | 0 / 11 | |
| 3.1.36 | 0 / 11 | |
| 3.1.35 | 0 / 11 | |
| 3.1.34 | 0 / 11 | |
| 3.1.33 | 0 / 11 | |
| 3.1.32 | 0 / 11 | |
| 3.1.31 | 0 / 11 | |
| 3.1.30 | 0 / 11 | |
| 3.1.29 | 0 / 11 | |
| 3.1.28 | 0 / 11 | |
| 3.1.27 | 0 / 11 | |
| 3.1.26 | 0 / 11 | |
| 3.1.25 | 0 / 11 | |
| 3.1.24 | 0 / 11 | |
| 3.1.23 | 0 / 11 | |
| 3.1.22 | 0 / 11 | |
| 3.1.21 | 0 / 11 | |
| 3.1.20 | 0 / 11 | |
| 3.1.19 | 0 / 11 | |
| 3.1.18 | 0 / 11 | |
| 3.1.17 | 0 / 11 | |
| 3.1.16 | 0 / 11 | |
| 3.1.15 | 0 / 11 | |
| 3.1.14 | 0 / 11 |
v3.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.35
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leodka) than the most recent previously approved version (kasimir-dka) on 2025-10-16, but leodka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.34
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-10-09, but kasimir-dka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.33
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-09-23, but kasimir-dka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-04-30, but kasimir-dka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.14
2 findingsThis version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-31. It has since remained available on npm for 473 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.