@observablehq/framework
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:markdown-it | AI (dependencies): Well-known Markdown parser; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:fast-array-diff | AI (dependencies): Small utility library; no malicious signals. | ai | |
| dependencies | unvetted-dep:@observablehq/inputs | AI (dependencies): First-party ObservableHQ dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@observablehq/inspector | AI (dependencies): First-party ObservableHQ dependency; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established ObservableHQ package; provenance absence is consistent across all versions and not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.13.4 | 44 / 33 | |
| 1.13.3 | 44 / 34 | |
| 1.13.2 | 44 / 34 | |
| 1.13.1 | 44 / 34 | |
| 1.13.0 | 44 / 34 | |
| 1.12.0 | 42 / 34 | |
| 1.11.0 | 40 / 34 | |
| 1.10.1 | 39 / 35 | |
| 1.10.0 | 38 / 35 | |
| 1.9.0 | 38 / 35 | |
| 1.8.0 | 37 / 36 | |
| 1.7.1 | 37 / 36 |
v1.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.