@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 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 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 |
v4.76.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.75.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.75.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.75.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.74.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.73.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.71.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.70.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.70.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.70.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.69.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.68.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.67.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.65.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.63.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.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.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.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.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.59.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.58.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.57.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.57.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.57.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.57.3
2 findingsScript: cd playground && npm ci --ignore-scripts || true
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.