@likec4/layouts
Layout algorithms for LikeC4 views
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/chunks/sequence.mjs | AI (source-diff): Minified rolldown/tsdown bundle output, readable logic, no malicious behavior. | ai | |
| phantom-deps | phantom-dep:unstorage | AI (phantom-deps): Used via config/runtime resolution, not a direct import; benign for this package. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is benign for a scoped package with clear repo and exports. | ai | |
| phantom-deps | phantom-dep:esm-env | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| provenance | missing-githead | AI (provenance): Minor publish-env metadata gap, no behavioral evidence of compromise for this trusted publisher. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation; legitimate CI/CD migration. | ai | |
| dependencies | unvetted-dep:vecti | AI (dependencies): vecti is a vector math library consistent with layout tooling; stable dependency for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): vecti is a benign vector math utility; no malicious indicators found. | ai | |
| phantom-deps | phantom-dep:fast-equals | AI (phantom-deps): Monorepo package; declared deps used transitively, not directly imported. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo sub-package; sparse README and no keywords are expected for internal layout packages. | ai | |
| phantom-deps | phantom-dep:indent-string | AI (phantom-deps): Monorepo package; declared deps used transitively, not directly imported. | ai | |
| phantom-deps | phantom-dep:strip-indent | AI (phantom-deps): Monorepo package; declared deps used transitively, not directly imported. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 1.59.2 | 20 / 10 | |
| 1.59.1 | 20 / 10 | |
| 1.59.0 | 20 / 10 | |
| 1.58.0 | 19 / 10 | |
| 1.57.0 | 19 / 10 | |
| 1.56.0 | 16 / 8 | |
| 1.55.1 | 16 / 8 | |
| 1.55.0 | 16 / 8 | |
| 1.54.0 | 16 / 8 | |
| 1.53.0 | 16 / 8 | |
| 1.52.0 | 16 / 8 | |
| 1.51.0 | 16 / 8 | |
| 1.50.0 | 16 / 8 | |
| 1.49.0 | 16 / 8 | |
| 1.48.0 | 16 / 8 | |
| 1.47.0 | 16 / 8 | |
| 1.46.4 | 16 / 8 | |
| 1.46.3 | 16 / 8 | |
| 1.46.2 | 16 / 8 | |
| 1.46.0 | 16 / 8 | |
| 1.45.0 | 17 / 8 | |
| 1.44.0 | 17 / 8 | |
| 1.43.0 | 17 / 8 | |
| 1.42.1 | 17 / 8 | |
| 1.42.0 | 17 / 8 | |
| 1.41.0 | 18 / 7 | |
| 1.40.0 | 18 / 7 | |
| 1.39.5 | 18 / 7 | |
| 1.39.4 | 18 / 7 | |
| 1.39.3 | 18 / 7 | |
| 1.39.2 | 18 / 7 | |
| 1.39.1 | 18 / 7 | |
| 1.39.0 | 18 / 7 | |
| 1.38.1 | 18 / 7 | |
| 1.38.0 | 18 / 7 | |
| 1.37.0 | 18 / 7 | |
| 1.36.1 | 18 / 7 | |
| 1.36.0 | 18 / 7 | |
| 1.35.0 | 18 / 7 | |
| 1.34.2 | 17 / 7 | |
| 1.34.1 | 17 / 7 | |
| 1.34.0 | 17 / 7 | |
| 1.33.0 | 17 / 7 | |
| 1.32.2 | 17 / 7 | |
| 1.32.1 | 16 / 7 | |
| 1.32.0 | 16 / 7 | |
| 1.31.0 | 16 / 7 | |
| 1.30.0 | 16 / 7 | |
| 1.29.1 | 16 / 7 | |
| 1.29.0 | 16 / 7 | |
| 1.26.2 | 16 / 7 | |
| 1.26.1 | 16 / 7 | |
| 1.26.0 | 16 / 7 | |
| 1.25.1 | 16 / 7 | |
| 1.25.0 | 16 / 7 | |
| 1.24.1 | 16 / 7 | |
| 1.24.0 | 16 / 7 | |
| 1.23.1 | 16 / 7 | |
| 1.23.0 | 16 / 7 | |
| 1.22.1 | 15 / 6 | |
| 1.22.0 | 15 / 6 | |
| 1.21.1 | 15 / 6 | |
| 1.21.0 | 14 / 6 | |
| 1.20.3 | 14 / 6 | |
| 1.20.2 | 12 / 6 | |
| 1.20.1 | 12 / 6 | |
| 1.20.0 | 12 / 6 | |
| 1.19.2 | 12 / 6 | |
| 1.19.1 | 12 / 6 | |
| 1.19.0 | 12 / 6 | |
| 1.18.0 | 12 / 6 | |
| 1.17.1 | 12 / 6 | |
| 1.17.0 | 12 / 6 | |
| 1.16.0 | 12 / 6 | |
| 1.15.1 | 12 / 6 | |
| 1.15.0 | 12 / 6 | |
| 1.14.0 | 12 / 6 | |
| 1.13.0 | 12 / 6 | |
| 1.12.2 | 12 / 6 | |
| 1.12.1 | 12 / 6 | |
| 1.12.0 | 12 / 6 | |
| 1.11.0 | 12 / 6 | |
| 1.10.1 | 13 / 6 | |
| 1.10.0 | 13 / 6 | |
| 1.9.0 | 13 / 6 | |
| 1.8.1 | 13 / 5 | |
| 1.8.0 | 13 / 5 | |
| 1.7.4 | 13 / 5 | |
| 1.7.3 | 13 / 5 | |
| 1.7.2 | 13 / 5 | |
| 1.7.1 | 13 / 5 | |
| 1.7.0 | 13 / 5 | |
| 1.6.1 | 10 / 7 | |
| 1.6.0 | 10 / 7 | |
| 1.5.0 | 10 / 7 | |
| 1.4.0 | 10 / 7 | |
| 1.3.0 | 10 / 7 | |
| 1.2.2 | 10 / 7 | |
| 1.2.1 | 10 / 7 | |
| 1.2.0 | 10 / 6 |
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.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.29.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.29.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.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage 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.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.