← Home

@mescius/spread-sheets

npm Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mescius

Keywords

spread-sheetsjavascript spreadsheetjavascript excelexcel iosheetssheetjavascriptexcelmesciusspreadjsReact spreadsheetAngular spreadsheetVue spreadsheetOnline excelOnline spreadsheetPivotTable spreadsheetOnline spreadsheet designer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/gc.spread.sheets.all.min.js AI (source-diff): Minified commercial spreadsheet bundle; long strings are expected in this large dist file. ai
publish-pattern dormant-publish AI (publish-pattern): MESCIUS publishes major versions periodically; dormancy reflects release cadence, not takeover. ai

Versions (showing 9 of 9)

Version Deps Published
19.1.1 0 / 0
19.1.0 0 / 0
19.0.6 0 / 0
19.0.5 0 / 0
19.0.4 0 / 0
19.0.3 0 / 0
19.0.2 0 / 0
19.0.1 0 / 0
19.0.0 0 / 0

v19.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.6

2 findings
HIGH Long encoded string in modified file: dist/gc.spread.sheets.all.min.js source-diff

Modified file contains 19 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.5

2 findings
HIGH Long encoded string in modified file: dist/gc.spread.sheets.all.min.js source-diff

Modified file contains 19 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.4

2 findings
HIGH Long encoded string in modified file: dist/gc.spread.sheets.all.min.js source-diff

Modified file contains 19 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.3

2 findings
HIGH Long encoded string in modified file: dist/gc.spread.sheets.all.min.js source-diff

Modified file contains 19 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.2

2 findings
HIGH Long encoded string in modified file: dist/gc.spread.sheets.all.min.js source-diff

Modified file contains 19 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v19.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.