@opengis/fastify-table
core-plugins
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): fastify is a declared runtime dependency and core framework for this plugin package; phantom-dep is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with consistent publish history; lack of provenance is expected for this publisher. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a well-known templating library; stable legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known markdown parser; stable legitimate dependency for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): minio is a well-known S3 client; addition is consistent with package's storage/backend purpose. | ai | |
| phantom-deps | phantom-dep:uglify-js | AI (phantom-deps): uglify-js is listed as a runtime dep and used via build scripts (compress.js); phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 2.5.26 | 32 / 16 | |
| 2.5.25 | 32 / 16 | |
| 2.5.24 | 32 / 16 | |
| 2.5.23 | 32 / 16 | |
| 2.5.22 | 32 / 16 | |
| 2.5.21 | 32 / 16 | |
| 2.5.20 | 32 / 16 | |
| 2.5.18 | 32 / 16 | |
| 2.5.17 | 32 / 16 | |
| 2.5.16 | 32 / 16 | |
| 2.5.15 | 32 / 16 | |
| 2.5.14 | 32 / 16 | |
| 2.5.13 | 32 / 16 | |
| 2.5.11 | 32 / 16 | |
| 2.5.10 | 32 / 16 | |
| 2.5.9 | 32 / 16 | |
| 2.5.7 | 32 / 16 | |
| 2.5.3 | 31 / 16 | |
| 2.4.0 | 32 / 16 | |
| 2.3.6 | 31 / 16 | |
| 2.3.5 | 31 / 16 | |
| 2.2.12 | 31 / 16 | |
| 2.2.11 | 31 / 16 | |
| 2.2.5 | 31 / 16 | |
| 2.2.4 | 31 / 16 | |
| 2.2.3 | 31 / 16 | |
| 2.2.2 | 31 / 16 | |
| 2.2.0 | 31 / 16 | |
| 2.1.19 | 31 / 16 | |
| 2.1.15 | 31 / 16 | |
| 2.1.14 | 31 / 16 | |
| 2.1.10 | 31 / 16 | |
| 2.1.8 | 31 / 16 | |
| 2.1.6 | 31 / 16 | |
| 2.1.5 | 31 / 16 | |
| 2.1.4 | 31 / 16 | |
| 2.1.1 | 31 / 16 | |
| 2.0.157 | 31 / 16 | |
| 2.0.155 | 31 / 16 | |
| 2.0.154 | 31 / 16 | |
| 2.0.152 | 31 / 16 | |
| 2.0.148 | 31 / 16 | |
| 2.0.147 | 31 / 16 | |
| 2.0.145 | 31 / 16 | |
| 2.0.144 | 31 / 16 | |
| 2.0.143 | 31 / 16 | |
| 2.0.140 | 31 / 16 | |
| 2.0.137 | 31 / 16 | |
| 2.0.132 | 31 / 16 | |
| 2.0.128 | 31 / 16 | |
| 2.0.123 | 31 / 16 |
v2.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (setebosu) than the most recent previously approved version (andrii.cherin) on 2026-07-07, but setebosu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.5.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andrii.cherin) than the most recent previously approved version (setebosu) on 2026-07-04, but andrii.cherin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.