@mml-io/observable-dom
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:canvas | AI (dependencies): canvas is a well-known native rendering lib, legitimate for DOM/canvas emulation. | ai | |
| phantom-deps | phantom-dep:canvas | AI (phantom-deps): canvas likely used via jsdom config, not direct import; heuristic FP. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package metadata gaps, not spam. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 4 / 2 | |
| 0.19.6 | 4 / 2 | |
| 0.19.5 | 3 / 2 | |
| 0.19.4 | 3 / 2 | |
| 0.19.3 | 3 / 2 | |
| 0.19.2 | 3 / 2 | |
| 0.19.1 | 3 / 2 | |
| 0.19.0 | 3 / 2 | |
| 0.18.1 | 3 / 2 | |
| 0.18.0 | 3 / 2 | |
| 0.17.1 | 3 / 2 | |
| 0.17.0 | 3 / 2 |
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.