jspreadsheet
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @jspreadsheet/formula-pro is a first-party scoped dep from the same vendor; not a suspicious third-party addition. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance absence is common and not a disqualifier for mature projects. | ai | |
| dependencies | unvetted-dep:@jspreadsheet/formula | AI (dependencies): First-party scoped dep from the same jspreadsheet org; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:jsuites | AI (dependencies): jsuites is the canonical companion UI library for jspreadsheet; stable first-party dependency across all versions. | ai | |
| dependencies | unvetted-dep:@jspreadsheet/formula-pro | AI (dependencies): First-party formula engine from the jspreadsheet org; stable companion dependency across versions. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 12.7.0 | 2 / 0 | |
| 12.6.1 | 2 / 0 | |
| 12.6.0 | 2 / 0 | |
| 12.5.1 | 2 / 0 | |
| 12.5.0 | 2 / 0 | |
| 12.4.6 | 2 / 0 | |
| 12.4.5 | 2 / 0 | |
| 12.4.4 | 2 / 0 | |
| 12.4.2 | 2 / 0 | |
| 12.4.1 | 2 / 0 | |
| 12.4.0 | 2 / 0 | |
| 12.3.12 | 2 / 0 | |
| 12.3.11 | 2 / 0 | |
| 12.3.10 | 2 / 0 | |
| 12.3.9 | 2 / 0 | |
| 12.3.8 | 2 / 0 | |
| 12.3.7 | 2 / 0 | |
| 12.3.6 | 2 / 0 | |
| 12.3.4 | 2 / 0 | |
| 12.3.3 | 2 / 0 | |
| 12.3.2 | 2 / 0 | |
| 12.3.1 | 2 / 0 | |
| 12.3.0 | 2 / 0 | |
| 12.2.9 | 2 / 0 | |
| 12.2.8 | 2 / 0 | |
| 12.2.6 | 2 / 0 | |
| 12.2.5 | 2 / 0 | |
| 12.2.4 | 2 / 0 | |
| 12.2.3 | 2 / 0 | |
| 12.2.2 | 2 / 0 | |
| 12.2.1 | 2 / 0 | |
| 12.2.0 | 2 / 0 | |
| 12.1.1 | 2 / 0 | |
| 12.1.0 | 2 / 0 | |
| 12.0.8 | 2 / 0 | |
| 12.0.7 | 2 / 0 | |
| 12.0.6 | 2 / 0 | |
| 12.0.5 | 2 / 0 | |
| 12.0.4 | 2 / 0 | |
| 12.0.3 | 2 / 0 | |
| 12.0.2 | 2 / 0 | |
| 12.0.1 | 2 / 0 | |
| 12.0.0 | 2 / 0 | |
| 11.30.1 | 2 / 0 | |
| 11.30.0 | 2 / 0 | |
| 11.29.0 | 2 / 0 | |
| 11.28.3 | 2 / 0 | |
| 11.28.2 | 2 / 0 | |
| 11.28.1 | 2 / 0 | |
| 11.28.0 | 2 / 0 |
v12.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.