@acrodata/gui
JSON powered GUI for configurable panels.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): No material changes vs prior version; same publisher with 48 approved packages; dormancy consistent with maintenance cadence. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @acrodata/gui; no relation to got. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @acrodata/gui; no relation to joi. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @acrodata/gui; no relation to yup. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @acrodata/gui; no relation to uuid. Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency used implicitly by Angular/TypeScript compiled output; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 44 versions; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in ejsTmpl template engine for dynamic form rendering; standard pattern for this type of library. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 4 / 0 | |
| 3.2.1 | 4 / 0 | |
| 3.2.0 | 4 / 0 | |
| 3.1.0 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 | |
| 2.10.0 | 4 / 0 |
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.