@node-projects/layout2vector
DOM → Geometry → DXF/PDF/PNG library
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-min.js | AI (source-diff): esbuild-minified bundle output from documented build script, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Compiled writer/extractor output matching stated PDF/PNG/DXF conversion functionality. | ai | |
| dependencies | unvetted-dep:@tarikjabiri/dxf | AI (dependencies): DXF writer lib matches package's stated DXF export function. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Sibling org package (acad-ts) added, consistent with CAD/vector functionality. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has strong track record; lack of provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is explicitly used in the bundle script in package.json; not a true phantom dependency. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 5.21.0 | 2 / 6 | |
| 5.20.0 | 4 / 5 | |
| 5.19.0 | 4 / 5 | |
| 5.18.0 | 3 / 5 | |
| 5.17.0 | 3 / 5 | |
| 5.16.0 | 3 / 5 | |
| 5.15.0 | 3 / 5 | |
| 5.14.0 | 3 / 5 | |
| 5.13.0 | 3 / 5 | |
| 5.12.0 | 3 / 5 | |
| 5.11.0 | 3 / 5 | |
| 5.9.0 | 3 / 5 | |
| 5.8.0 | 3 / 5 | |
| 5.7.0 | 3 / 5 | |
| 5.6.0 | 3 / 5 | |
| 5.4.0 | 3 / 5 | |
| 5.3.0 | 3 / 5 | |
| 5.2.0 | 3 / 5 | |
| 5.1.0 | 3 / 5 | |
| 5.0.0 | 3 / 5 | |
| 4.9.0 | 3 / 5 | |
| 4.8.0 | 3 / 4 | |
| 4.7.0 | 3 / 4 | |
| 4.6.1 | 3 / 4 | |
| 4.6.0 | 3 / 4 | |
| 4.5.0 | 2 / 4 | |
| 4.4.0 | 2 / 4 | |
| 4.3.0 | 2 / 4 | |
| 4.2.0 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.0 | 2 / 4 | |
| 3.0.0 | 2 / 4 | |
| 2.0.0 | 2 / 4 | |
| 1.27.0 | 2 / 4 | |
| 1.26.0 | 2 / 4 | |
| 1.25.0 | 2 / 4 | |
| 1.24.0 | 2 / 4 | |
| 1.23.0 | 2 / 4 | |
| 1.22.0 | 1 / 4 | |
| 1.21.0 | 1 / 4 | |
| 1.20.0 | 1 / 4 | |
| 1.19.0 | 1 / 4 | |
| 1.17.0 | 1 / 4 | |
| 1.16.0 | 1 / 4 | |
| 1.15.0 | 1 / 4 | |
| 1.14.0 | 1 / 4 | |
| 1.13.0 | 1 / 4 | |
| 1.12.0 | 1 / 4 | |
| 1.11.0 | 1 / 4 | |
| 1.9.0 | 1 / 4 | |
| 1.8.0 | 1 / 4 |
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.