@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 |
|---|---|---|---|---|
| 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:strip-indent | AI (phantom-deps): Monorepo package; declared deps used transitively, not directly imported. | ai | |
| phantom-deps | phantom-dep:indent-string | AI (phantom-deps): Monorepo package; declared deps used transitively, not directly imported. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 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.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.1 | 18 / 7 | |
| 1.39.0 | 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 |
v1.58.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.57.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.56.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.55.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.55.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.54.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.49.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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.47.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.