read-excel-file
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:bundle/read-excel-file.min.old.js | AI (source-diff): Minified rollup/terser browser bundle; benign build output for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across all prior versions. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 9.3.4 | 3 / 18 | |
| 9.3.3 | 3 / 18 | |
| 9.3.2 | 3 / 18 | |
| 9.3.1 | 3 / 18 | |
| 9.3.0 | 2 / 19 | |
| 9.2.0 | 3 / 20 | |
| 9.1.1 | 2 / 20 | |
| 9.1.0 | 2 / 20 | |
| 9.0.10 | 3 / 20 | |
| 9.0.9 | 3 / 20 | |
| 9.0.8 | 3 / 20 | |
| 9.0.7 | 3 / 20 | |
| 9.0.6 | 3 / 20 | |
| 9.0.5 | 3 / 20 | |
| 9.0.4 | 3 / 20 | |
| 9.0.3 | 3 / 20 | |
| 9.0.2 | 3 / 20 | |
| 9.0.1 | 3 / 20 | |
| 9.0.0 | 3 / 20 | |
| 8.0.3 | 3 / 20 | |
| 8.0.2 | 3 / 20 | |
| 8.0.1 | 3 / 20 | |
| 8.0.0 | 3 / 20 | |
| 7.0.3 | 3 / 20 | |
| 7.0.2 | 3 / 20 | |
| 7.0.1 | 3 / 20 | |
| 7.0.0 | 3 / 20 | |
| 6.0.3 | 3 / 20 | |
| 6.0.2 | 3 / 20 |
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.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.