@mml-io/networked-dom-protocol No license 28 versions

@mml-io/networked-dom-protocol

npm Repository Homepage

[![npm version](https://img.shields.io/npm/v/@mml-io/networked-dom-protocol.svg?style=flat)](https://www.npmjs.com/package/@mml-io/networked-dom-protocol)

28

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

marcuslongmuir

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	large-new-source-files	AI (source-diff): Legitimate protocol package growth from established @mml-io org, no executable/script risk.	ai	2026/07/18
source-diff	source-size-tripled	AI (source-diff): Small absolute size (41KB); consistent with normal feature growth, not a payload.	ai	2026/07/18
maintainer-change	maintainer-added	AI (maintainer-change): Publisher has long clean track record (118 approved pkgs); likely org team addition.	ai	2026/07/18
bogus-package	bogus-package	AI (bogus-package): Protocol/types-only scoped package; no deps, minimal README, and no repo link are expected for this kind of internal protocol definition package.	ai	2026/05/11

Versions (showing 28 of 28)

Version	Deps	Published
0.26.1	0 / 0	2026-03-11
0.26.0	0 / 0	2026-03-06
0.25.0	0 / 0	2026-02-18
0.24.1	0 / 0	2026-01-27
0.24.0	0 / 0	2026-01-27
0.23.1	0 / 0	2025-12-16
0.23.0	0 / 0	2025-10-29
0.22.0	0 / 0	2025-10-14
0.21.3	0 / 0	2025-09-26
0.21.2	0 / 0	2025-09-22
0.21.1	0 / 0	2025-09-18
0.21.0	0 / 0	2025-09-16
0.20.0	0 / 0	2025-07-17
0.19.7	0 / 0	2025-04-22
0.19.6	0 / 0	2025-03-19
0.19.5	0 / 0	2025-03-02
0.19.4	0 / 0	2025-03-02
0.19.3	0 / 0	2025-02-07
0.19.2	0 / 0	2025-02-05
0.19.1	0 / 0	2025-01-30
0.19.0	0 / 0	2025-01-20
0.18.1	0 / 0	2024-10-07
0.18.0	0 / 0	2024-08-19
0.17.1	0 / 0	2024-08-02
0.17.0	0 / 0	2024-07-17
0.16.1	0 / 0	2024-07-03
0.16.0	0 / 0	2024-06-26
0.15.0	0 / 0	2024-05-29

v0.19.7

1 finding

LOW No provenance attestation provenance

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

v0.19.6

1 finding

LOW No provenance attestation provenance

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

v0.19.5

1 finding

LOW No provenance attestation provenance

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

v0.19.4

1 finding

LOW No provenance attestation provenance

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

v0.19.3

1 finding

LOW No provenance attestation provenance

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

v0.19.2

1 finding

LOW No provenance attestation provenance

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

v0.19.1

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.1

1 finding

LOW No provenance attestation provenance

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

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.

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.1

1 finding

LOW No provenance attestation provenance

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

v0.16.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.15.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.