@tricoteuses/senat AGPL-3.0-or-later 29 versions

@tricoteuses/senat

npm Repository Homepage

Handle French Sénat's open data

29

Versions

AGPL-3.0-or-later

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

eraviarthjoninhboisgibaultdregop

Keywords

Franceopen dataParliamentSénat

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:tsx	AI (phantom-deps): tsx is a declared runtime dep used in npm scripts; phantom-dep false positive for this package.	ai	2026/05/04
install-scripts	install-script:postinstall	AI (install-scripts): postinstall runs patch-package, a standard dev dependency patching tool; stable pattern for this package.	ai	2026/04/30
semgrep	semgrep:env-spread	AI (semgrep): Intentional pattern: spreading process.env to pass PG connection vars to psql in a DB tooling script.	ai	2026/04/29
semgrep	semgrep:hex-decode	AI (semgrep): Decodes SQL statements from open-data files for local DB ingestion; consistent with ETL purpose of this package.	ai	2026/04/29
dependencies	unvetted-dep:windows-1252	AI (dependencies): windows-1252 is a legitimate charset decoder needed for French government open data files encoded in that charset.	ai	2026/04/29

Versions (showing 29 of 29)

Version	Deps	Published
3.1.11	14 / 22	2026-05-11
3.1.10	14 / 22	2026-05-07
3.1.9	14 / 22	2026-05-07
3.1.8	14 / 22	2026-05-04
3.1.6	14 / 22	2026-04-29
3.1.5	14 / 22	2026-04-27
3.1.3	14 / 22	2026-04-24
3.1.2	13 / 21	2026-04-19
3.1.1	13 / 21	2026-04-17
3.1.0	13 / 21	2026-04-12
3.0.2	13 / 18	2026-04-05
3.0.0	13 / 20	2026-04-04
2.23.0	13 / 17	2026-04-02
2.22.16	16 / 20	2026-03-13
2.22.15	16 / 20	2026-03-12
2.22.14	16 / 20	2026-03-12
2.22.13	16 / 20	2026-03-11
2.22.10	16 / 20	2026-03-06
2.22.7	16 / 20	2026-03-02
2.21.4	17 / 19	2026-02-05
2.21.3	17 / 19	2026-02-04
2.21.2	17 / 19	2026-02-04
2.21.1	17 / 19	2026-02-02
2.21.0	16 / 19	2026-02-02
2.20.35	17 / 19	2026-02-02
2.20.34	17 / 19	2026-02-02
2.19.5	15 / 19	2025-11-16
2.19.3	15 / 19	2025-11-12
2.16.2	14 / 19	2025-11-03

v3.1.11

1 finding

LOW No provenance attestation provenance

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

v3.1.10

1 finding

LOW No provenance attestation provenance

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

v3.1.9

1 finding

LOW No provenance attestation provenance

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

v3.1.8

1 finding

LOW No provenance attestation provenance

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

v3.1.6

2 findings

HIGH Publisher changed: dregop → hboisgibault (on 2026-04-29) provenance

This version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.1.3

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.

v3.1.2

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.

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.2

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.

v3.0.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: patch-package

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

v2.22.16

1 finding

LOW No provenance attestation provenance

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

v2.22.15

1 finding

LOW No provenance attestation provenance

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

v2.22.14

1 finding

LOW No provenance attestation provenance

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

v2.22.13

1 finding

LOW No provenance attestation provenance

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

v2.22.10

1 finding

LOW No provenance attestation provenance

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

v2.22.7

1 finding

LOW No provenance attestation provenance

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

v2.21.4

1 finding

LOW No provenance attestation provenance

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

v2.21.3

1 finding

LOW No provenance attestation provenance

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

v2.21.2

1 finding

LOW No provenance attestation provenance

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

v2.21.1

1 finding

LOW No provenance attestation provenance

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

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

v2.20.35

1 finding

LOW No provenance attestation provenance

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

v2.20.34

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.19.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.19.3

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

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.