@ag-grid-enterprise/excel-export
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): ag-grid enterprise packages consistently publish without Sigstore provenance; stable pattern for this package family. | ai | |
| dependencies | unvetted-dep:@ag-grid-community/core | AI (dependencies): Sibling ag-grid monorepo dependency; expected and stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@ag-grid-enterprise/core | AI (dependencies): Sibling ag-grid monorepo dependency; expected and stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@ag-grid-community/csv-export | AI (dependencies): Sibling ag-grid monorepo dependency; expected and stable across all versions of this package. | ai | |
| license | uncommon-license:Commercial | AI (license): ag-grid enterprise packages are commercially licensed by design; stable for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 32.3.9 | 3 / 3 | |
| 32.3.8 | 3 / 3 | |
| 32.3.7 | 3 / 3 | |
| 32.3.6 | 3 / 3 | |
| 32.3.5 | 3 / 3 | |
| 32.3.4 | 3 / 3 | |
| 32.3.3 | 3 / 3 | |
| 32.3.2 | 3 / 3 | |
| 32.3.1 | 3 / 3 | |
| 32.3.0 | 3 / 3 | |
| 32.2.2 | 3 / 3 | |
| 32.2.1 | 3 / 3 | |
| 32.2.0 | 3 / 3 | |
| 32.1.0 | 3 / 3 | |
| 32.0.2 | 3 / 3 | |
| 32.0.1 | 3 / 3 | |
| 32.0.0 | 3 / 3 |
v32.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.