vue-grid-layout
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No behavior change; likely publish tooling variance for a stable long-lived package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-established package with sporadic release cadence, no other risk signal. | ai | |
| phantom-deps | phantom-dep:@interactjs/dev-tools | AI (phantom-deps): Website package.json artifact; config-only reference. | ai | |
| phantom-deps | phantom-dep:@interactjs/modifiers | AI (phantom-deps): Website package.json artifact; config-only reference. | ai | |
| phantom-deps | phantom-dep:@interactjs/auto-start | AI (phantom-deps): Website package.json artifact; config-only reference. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires inside bundled vue.js in website/docs public folder, not library source code. | ai | |
| phantom-deps | phantom-dep:@interactjs/auto-scroll | AI (phantom-deps): Website package.json artifact; config-only reference. | ai | |
| phantom-deps | phantom-dep:element-resize-detector | AI (phantom-deps): Website package.json artifact; config-only reference. | ai | |
| phantom-deps | phantom-dep:@interactjs/interactjs | AI (phantom-deps): Website package.json artifact; config-only reference. | ai | |
| phantom-deps | phantom-dep:@interactjs/actions | AI (phantom-deps): Website package.json artifact; interactjs deps are referenced in config only, not imported. | ai |
v2.3.12
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: gmsa.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.