@likec4/diagram
A React component library for rendering software architecture diagrams
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI/CD publisher with SLSA provenance; legitimate automated release pipeline. | ai | |
| provenance | missing-githead | AI (provenance): Minor publish metadata gap, no diff/behavior change; trusted long-running publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Well-known xstate ecosystem libs added for a documented state-machine migration. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase matches legit xstate migration with generated .d.ts files, not injected code. | ai | |
| phantom-deps | phantom-dep:@xstate/store | AI (phantom-deps): Used indirectly via xstate config/setup, false positive for this monorepo package. | ai | |
| dependencies | unvetted-dep:@nanostores/react | AI (dependencies): Legitimate nanostores ecosystem package; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@nanostores/media-query | AI (dependencies): Legitimate nanostores ecosystem package; no malicious indicators. | ai | |
| phantom-deps | phantom-dep:defu | AI (phantom-deps): Build-time/config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nanostores/media-query | AI (phantom-deps): Build-time/config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lume/kiwi | AI (phantom-deps): Build-time/config reference; stable false positive for this package. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 1.59.2 | 29 / 17 | |
| 1.59.1 | 29 / 17 | |
| 1.59.0 | 29 / 17 | |
| 1.58.0 | 31 / 17 | |
| 1.57.0 | 29 / 20 | |
| 1.56.0 | 30 / 19 | |
| 1.55.1 | 29 / 21 | |
| 1.55.0 | 29 / 21 | |
| 1.54.0 | 29 / 21 | |
| 1.53.0 | 29 / 21 | |
| 1.52.0 | 29 / 21 | |
| 1.51.0 | 29 / 21 | |
| 1.50.0 | 29 / 21 | |
| 1.49.0 | 29 / 21 | |
| 1.48.0 | 25 / 21 | |
| 1.47.0 | 25 / 21 | |
| 1.46.4 | 25 / 21 | |
| 1.46.3 | 25 / 21 | |
| 1.46.2 | 25 / 21 | |
| 1.46.0 | 25 / 21 | |
| 1.45.0 | 25 / 21 | |
| 1.44.0 | 24 / 21 | |
| 1.43.0 | 23 / 21 | |
| 1.42.1 | 23 / 21 | |
| 1.42.0 | 23 / 21 | |
| 1.26.2 | 21 / 15 | |
| 1.26.1 | 21 / 15 | |
| 1.26.0 | 21 / 15 | |
| 1.25.1 | 21 / 15 | |
| 1.25.0 | 21 / 15 | |
| 1.24.1 | 22 / 14 | |
| 1.24.0 | 22 / 14 | |
| 1.23.1 | 22 / 14 | |
| 1.23.0 | 22 / 14 | |
| 1.20.1 | 20 / 18 | |
| 1.20.0 | 20 / 18 | |
| 1.19.2 | 17 / 18 | |
| 1.19.1 | 17 / 18 | |
| 1.19.0 | 17 / 18 | |
| 1.18.0 | 21 / 13 | |
| 1.17.1 | 20 / 13 | |
| 1.17.0 | 20 / 11 | |
| 1.16.0 | 20 / 11 | |
| 1.15.1 | 20 / 11 | |
| 1.15.0 | 20 / 11 | |
| 1.14.0 | 20 / 11 | |
| 1.13.0 | 20 / 11 | |
| 1.12.2 | 20 / 11 | |
| 1.12.1 | 20 / 11 | |
| 1.12.0 | 20 / 11 | |
| 1.9.0 | 19 / 17 | |
| 1.8.1 | 16 / 20 | |
| 1.8.0 | 16 / 20 | |
| 1.7.4 | 16 / 20 | |
| 1.7.3 | 16 / 20 | |
| 1.7.2 | 16 / 20 | |
| 1.7.1 | 16 / 20 | |
| 1.7.0 | 16 / 20 | |
| 1.6.1 | 16 / 20 | |
| 1.6.0 | 12 / 25 | |
| 1.5.0 | 12 / 25 | |
| 1.4.0 | 12 / 25 | |
| 1.3.0 | 12 / 25 | |
| 1.2.2 | 9 / 27 | |
| 1.2.1 | 9 / 27 | |
| 1.2.0 | 9 / 26 | |
| 1.1.1 | 8 / 24 | |
| 1.1.0 | 7 / 23 | |
| 1.0.2 | 7 / 23 | |
| 1.0.1 | 7 / 23 | |
| 1.0.0 | 9 / 21 |
v1.59.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (davydkov) on 2026-01-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.47.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (davydkov) on 2026-01-04, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.46.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (davydkov) on 2025-12-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.46.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: davydkov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.