@opengis/fastify-table ISC 51 versions

@opengis/fastify-table

npm

core-plugins

51

Versions

ISC

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

evheniihavryliukandrii.cherinsetebosurapax.deusmchernenkoserebasikkartem_maniakinaponaskofarizov_maximbohdana_usenko

Keywords

fastifytablecrudauthpgbackend

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	2026/06/02
provenance	no-provenance	AI (provenance): Long-established package with consistent publish history; lack of provenance is expected for this publisher.	ai	2026/06/01
dependencies	unvetted-dep:handlebars	AI (dependencies): handlebars is a well-known templating library; stable legitimate dependency for this package.	ai	2026/06/01
dependencies	unvetted-dep:markdown-it	AI (dependencies): markdown-it is a well-known markdown parser; stable legitimate dependency for this package.	ai	2026/06/01
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	2026/05/30
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	2026/05/14

Versions (showing 51 of 72)

View all versions

Version	Deps	Published
2.4.0	32 / 16	2026-05-29
2.3.6	31 / 16	2026-05-22
2.3.5	31 / 16	2026-05-21
2.2.12	31 / 16	2026-05-18
2.2.11	31 / 16	2026-05-14
2.2.5	31 / 16	2026-05-07
2.2.4	31 / 16	2026-05-04
2.2.3	31 / 16	2026-05-04
2.2.2	31 / 16	2026-05-04
2.2.0	31 / 16	2026-04-30
2.1.19	31 / 16	2026-04-29
2.1.15	31 / 16	2026-04-28
2.1.14	31 / 16	2026-04-28
2.1.10	31 / 16	2026-04-24
2.1.8	31 / 16	2026-04-17
2.1.6	31 / 16	2026-04-10
2.1.5	31 / 16	2026-04-09
2.1.4	31 / 16	2026-04-08
2.1.1	31 / 16	2026-03-30
2.0.157	31 / 16	2026-03-18
2.0.155	31 / 16	2026-03-17
2.0.154	31 / 16	2026-03-16
2.0.152	31 / 16	2026-03-13
2.0.148	31 / 16	2026-03-09
2.0.147	31 / 16	2026-03-04
2.0.145	31 / 16	2026-02-24
2.0.144	31 / 16	2026-02-24
2.0.143	31 / 16	2026-02-23
2.0.140	31 / 16	2026-02-19
2.0.137	31 / 16	2026-02-17
2.0.132	31 / 16	2026-02-06
2.0.128	31 / 16	2026-01-29
2.0.123	31 / 16	2026-01-19
2.0.122	31 / 16	2026-01-19
2.0.121	31 / 16	2026-01-16
2.0.119	31 / 16	2026-01-14
2.0.113	31 / 16	2025-12-29
2.0.111	31 / 16	2025-12-29
2.0.106	31 / 16	2025-12-12
2.0.105	31 / 16	2025-12-11
2.0.100	31 / 16	2025-12-09
2.0.99	31 / 16	2025-12-09
2.0.98	31 / 16	2025-12-08
2.0.94	31 / 16	2025-11-27
2.0.92	31 / 16	2025-11-27
2.0.91	31 / 16	2025-11-27
2.0.89	31 / 16	2025-11-26
2.0.79	30 / 16	2025-11-18
2.0.76	30 / 16	2025-11-13
2.0.75	30 / 16	2025-11-13
2.0.73	30 / 16	2025-11-12

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.6

1 finding

LOW No provenance attestation provenance

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

v2.3.5

1 finding

LOW No provenance attestation provenance

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

v2.2.12

1 finding

LOW No provenance attestation provenance

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

v2.2.11

1 finding

LOW No provenance attestation provenance

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

v2.2.5

1 finding

LOW No provenance attestation provenance

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

v2.2.4

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.15

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.

v2.1.14

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.

v2.1.10

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.

v2.1.8

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.

v2.1.6

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.

v2.1.5

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.

v2.1.4

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.

v2.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.

v2.0.157

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.

v2.0.155

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.

v2.0.154

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.

v2.0.152

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.

v2.0.148

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.

v2.0.147

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.

v2.0.145

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.

v2.0.144

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.

v2.0.143

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.

v2.0.140

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.

v2.0.137

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.

v2.0.132

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.

v2.0.128

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.

v2.0.123

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.

v2.0.122

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.

v2.0.121

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.

v2.0.119

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.

v2.0.113

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.

v2.0.111

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.

v2.0.106

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.

v2.0.105

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.

v2.0.100

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.

v2.0.99

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.

v2.0.98

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.

v2.0.94

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.

v2.0.92

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.

v2.0.91

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.

v2.0.89

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.

v2.0.79

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.

v2.0.76

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.

v2.0.75

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.

v2.0.73

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.