node-xlsx
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fixed local path concatenation, not variable/user-controlled module loading. | ai | |
| dependencies | unvetted-dep:xlsx | AI (dependencies): Official SheetJS CDN distribution, pinned version; known ecosystem pattern. | ai | |
| npm-metadata | url-dep:xlsx | AI (npm-metadata): Points to first-party SheetJS CDN, pinned version, not a hijack vector. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 1 / 10 | |
| 0.23.0 | 1 / 16 | |
| 0.22.0 | 1 / 16 | |
| 0.21.2 | 1 / 15 | |
| 0.21.1 | 1 / 15 | |
| 0.21.0 | 1 / 15 | |
| 0.20.0 | 1 / 15 | |
| 0.19.0 | 1 / 15 | |
| 0.18.0 | 1 / 15 | |
| 0.17.2 | 3 / 15 | |
| 0.17.1 | 3 / 15 | |
| 0.17.0 | 3 / 15 | |
| 0.16.2 | 3 / 15 | |
| 0.16.1 | 3 / 15 | |
| 0.16.0 | 2 / 16 | |
| 0.15.1 | 3 / 15 | |
| 0.15.0 | 2 / 15 | |
| 0.14.2 | 3 / 15 | |
| 0.14.1 | 2 / 15 | |
| 0.14.0 | 2 / 15 | |
| 0.13.1 | 2 / 15 | |
| 0.13.0 | 2 / 15 | |
| 0.12.2 | 3 / 15 | |
| 0.12.1 | 2 / 15 | |
| 0.12.0 | 1 / 15 | |
| 0.11.2 | 1 / 15 | |
| 0.11.1 | 1 / 15 | |
| 0.11.0 | 1 / 15 | |
| 0.10.0 | 1 / 15 | |
| 0.9.0 | 1 / 16 | |
| 0.7.4 | 1 / 16 | |
| 0.7.3 | 1 / 16 | |
| 0.7.2 | 1 / 16 | |
| 0.7.1 | 1 / 16 | |
| 0.7.0 | 1 / 16 | |
| 0.6.0 | 3 / 1 | |
| 0.5.1 | 3 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.2 | 1 / 1 |
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.