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 — 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across all prior versions. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 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.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.