@digital-ai/dot-illustrations
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is in demo/local-proxy.js, a dev-only proxy script, not shipped runtime code. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated GitHub Actions CI pipeline naturally produces rapid successive publishes; consistent with the publisher change. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.0.45 | 0 / 0 | |
| 2.0.43 | 0 / 0 | |
| 2.0.41 | 0 / 0 | |
| 2.0.37 | 0 / 0 | |
| 2.0.33 | 0 / 0 | |
| 2.0.32 | 0 / 0 | |
| 2.0.31 | 0 / 0 | |
| 2.0.30 | 0 / 0 | |
| 2.0.29 | 0 / 0 | |
| 2.0.28 | 0 / 0 | |
| 2.0.27 | 0 / 0 | |
| 2.0.26 | 0 / 0 | |
| 2.0.25 | 0 / 0 | |
| 2.0.24 | 0 / 0 | |
| 2.0.23 | 0 / 0 | |
| 2.0.22 | 0 / 0 | |
| 2.0.21 | 0 / 0 | |
| 2.0.20 | 0 / 0 | |
| 2.0.19 | 0 / 0 | |
| 2.0.18 | 0 / 0 | |
| 2.0.17 | 0 / 0 | |
| 2.0.16 | 0 / 0 | |
| 2.0.15 | 0 / 0 | |
| 2.0.14 | 0 / 0 | |
| 2.0.13 | 0 / 0 | |
| 2.0.12 | 0 / 0 | |
| 2.0.11 | 0 / 0 | |
| 2.0.10 | 0 / 0 | |
| 2.0.9 | 0 / 0 | |
| 2.0.8 | 0 / 0 | |
| 2.0.7 | 0 / 0 | |
| 2.0.6 | 0 / 0 | |
| 2.0.5 | 0 / 0 | |
| 2.0.4 | 0 / 0 | |
| 2.0.3 | 0 / 0 | |
| 2.0.2 | 0 / 0 | |
| 2.0.1 | 0 / 0 |
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.