@delon/abc
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:xlsx | AI (dependencies): xlsx is an intentional runtime dep for the ./xlsx export subpath; stable pattern across versions of this package. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @delon/abc is unrelated to ajv; levenshtein match is a false positive. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in lodop.mjs parses a structured response string into an array; input is from LODOP print API, not user-controlled arbitrary code. | ai | |
| phantom-deps | phantom-dep:xlsx | AI (phantom-deps): xlsx is declared as a dep and has a dedicated ./xlsx export entry; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 21.2.0 | 10 / 0 | |
| 21.1.0 | 11 / 0 | |
| 21.0.4 | 11 / 0 | |
| 21.0.3 | 11 / 0 | |
| 21.0.2 | 11 / 0 | |
| 21.0.0 | 11 / 0 | |
| 20.1.1 | 11 / 0 |
v21.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.