@diplodoc/transform
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall only sets up a local playground with npm ci --ignore-scripts; benign dev tooling, stable for this package. | ai | |
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is a well-known SVG optimizer; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a widely-used, well-maintained markdown parser; expected core dep. | ai | |
| dependencies | unvetted-dep:markdownlint-rule-helpers | AI (dependencies): markdownlint-rule-helpers is a standard linting utility; no risk. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@diplodoc/cut-extension | AI (dependencies): First-party diplodoc extension; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@diplodoc/file-extension | AI (dependencies): First-party diplodoc extension; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@diplodoc/tabs-extension | AI (dependencies): First-party diplodoc extension; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:get-root-node-polyfill | AI (dependencies): Tiny DOM polyfill; well-known and stable. | ai |
Versions (showing 100 of 108)
| Version | Deps | Published |
|---|---|---|
| 4.77.5 | 23 / 25 | |
| 4.77.4 | 23 / 25 | |
| 4.77.3 | 23 / 25 | |
| 4.77.2 | 23 / 25 | |
| 4.77.1 | 23 / 25 | |
| 4.77.0 | 23 / 25 | |
| 4.76.10 | 23 / 24 | |
| 4.76.9 | 23 / 24 | |
| 4.76.8 | 23 / 24 | |
| 4.76.7 | 23 / 24 | |
| 4.76.6 | 23 / 24 | |
| 4.76.5 | 23 / 24 | |
| 4.76.4 | 23 / 24 | |
| 4.76.3 | 23 / 24 | |
| 4.76.2 | 23 / 26 | |
| 4.76.1 | 23 / 26 | |
| 4.76.0 | 23 / 26 | |
| 4.75.5 | 23 / 26 | |
| 4.75.4 | 23 / 26 | |
| 4.75.3 | 23 / 26 | |
| 4.74.0 | 23 / 26 | |
| 4.73.2 | 23 / 26 | |
| 4.71.0 | 23 / 26 | |
| 4.70.4 | 23 / 26 | |
| 4.70.3 | 23 / 26 | |
| 4.70.1 | 23 / 26 | |
| 4.69.0 | 23 / 26 | |
| 4.68.1 | 23 / 26 | |
| 4.67.0 | 23 / 26 | |
| 4.65.3 | 23 / 25 | |
| 4.64.0 | 23 / 25 | |
| 4.63.7 | 23 / 25 | |
| 4.63.6 | 23 / 25 | |
| 4.63.5 | 23 / 25 | |
| 4.63.4 | 23 / 25 | |
| 4.63.2 | 23 / 25 | |
| 4.63.1 | 23 / 25 | |
| 4.63.0 | 23 / 25 | |
| 4.62.0 | 23 / 25 | |
| 4.61.1 | 23 / 25 | |
| 4.61.0 | 23 / 25 | |
| 4.60.4 | 23 / 25 | |
| 4.60.3 | 24 / 25 | |
| 4.60.2 | 24 / 24 | |
| 4.60.1 | 24 / 24 | |
| 4.60.0 | 24 / 24 | |
| 4.59.1 | 24 / 24 | |
| 4.59.0 | 24 / 24 | |
| 4.58.1 | 24 / 24 | |
| 4.58.0 | 24 / 24 | |
| 4.57.7 | 23 / 24 | |
| 4.57.6 | 23 / 24 | |
| 4.57.5 | 23 / 24 | |
| 4.57.3 | 23 / 24 | |
| 4.44.1 | 22 / 23 | |
| 4.44.0 | 22 / 23 | |
| 4.43.0 | 22 / 23 | |
| 4.42.4 | 22 / 23 | |
| 4.42.3 | 22 / 23 | |
| 4.42.2 | 22 / 23 | |
| 4.42.1 | 22 / 23 | |
| 4.42.0 | 22 / 23 | |
| 4.41.1 | 22 / 23 | |
| 4.41.0 | 21 / 24 | |
| 4.40.1 | 21 / 24 | |
| 4.40.0 | 21 / 24 | |
| 4.39.0 | 21 / 24 | |
| 4.38.2 | 20 / 24 | |
| 4.38.1 | 20 / 24 | |
| 4.38.0 | 20 / 24 | |
| 4.37.1 | 20 / 24 | |
| 4.37.0 | 20 / 24 | |
| 4.36.0 | 20 / 24 | |
| 4.35.0 | 20 / 24 | |
| 4.34.0 | 20 / 24 | |
| 4.33.0 | 20 / 24 | |
| 4.32.4 | 20 / 24 | |
| 4.32.3 | 20 / 24 | |
| 4.32.2 | 20 / 24 | |
| 4.32.1 | 20 / 24 | |
| 4.31.3 | 20 / 24 | |
| 4.31.2 | 20 / 24 | |
| 4.31.1 | 20 / 24 | |
| 4.31.0 | 20 / 24 | |
| 4.30.2 | 20 / 24 | |
| 4.30.1 | 20 / 24 | |
| 4.29.0 | 20 / 23 | |
| 4.28.3 | 19 / 23 | |
| 4.28.2 | 19 / 23 | |
| 4.28.1 | 19 / 23 | |
| 4.28.0 | 19 / 23 | |
| 4.27.0 | 19 / 23 | |
| 4.26.0 | 19 / 23 | |
| 4.25.1 | 19 / 23 | |
| 4.25.0 | 19 / 23 | |
| 4.24.0 | 19 / 23 | |
| 4.23.0 | 19 / 23 | |
| 4.22.0 | 19 / 23 | |
| 4.21.0 | 19 / 23 | |
| 4.20.0 | 19 / 23 |
v4.77.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.77.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.77.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.77.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.77.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.77.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.76.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.44.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.
v4.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.42.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.42.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.42.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.42.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.
v4.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.41.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.
v4.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.40.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.
v4.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.38.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.38.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.
v4.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.37.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.
v4.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.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.
v4.31.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.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.
v4.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.30.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.
v4.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.28.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.
v4.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.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.
v4.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.