@tricoteuses/senat
Handle French Sénat's open data
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@biryani/core | AI (dependencies): Long-standing dep of this author's own ecosystem, present across many versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fast-xml-parser is a well-known, widely-used XML parser fitting the package's scraping purpose. | ai | |
| source-diff | obfuscated-file:lib/raw_types_kysely/ameli.js | AI (source-diff): Auto-generated kysely-codegen type file with long sourcemap line. | ai | |
| source-diff | obfuscated-file:lib/aggregates.js | AI (source-diff): Babel/core-js transpiled build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/raw_types_kysely/debats.js | AI (source-diff): Auto-generated kysely-codegen type file with long sourcemap line. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth driven by generated DB schema/type files matching package's data-mirroring purpose. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Generated schema files for new dataset tables, consistent with package function. | ai | |
| 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 | |
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs patch-package, a standard dev dependency patching tool; stable pattern for this package. | ai | |
| 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 | |
| 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 | |
| semgrep | semgrep:env-spread | AI (semgrep): Intentional pattern: spreading process.env to pass PG connection vars to psql in a DB tooling script. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 3.1.23 | 15 / 23 | |
| 3.1.22 | 15 / 23 | |
| 3.1.21 | 14 / 22 | |
| 3.1.20 | 14 / 22 | |
| 3.1.19 | 14 / 22 | |
| 3.1.18 | 14 / 22 | |
| 3.1.17 | 14 / 22 | |
| 3.1.16 | 14 / 22 | |
| 3.1.15 | 14 / 22 | |
| 3.1.12 | 14 / 22 | |
| 3.1.11 | 14 / 22 | |
| 3.1.10 | 14 / 22 | |
| 3.1.9 | 14 / 22 | |
| 3.1.8 | 14 / 22 | |
| 3.1.7 | 14 / 22 | |
| 3.1.6 | 14 / 22 | |
| 3.1.5 | 14 / 22 | |
| 3.1.4 | 14 / 22 | |
| 3.1.3 | 14 / 22 | |
| 3.1.2 | 13 / 21 | |
| 3.1.1 | 13 / 21 | |
| 3.1.0 | 13 / 21 | |
| 3.0.2 | 13 / 18 | |
| 3.0.0 | 13 / 20 | |
| 2.23.0 | 13 / 17 | |
| 2.22.16 | 16 / 20 | |
| 2.22.15 | 16 / 20 | |
| 2.22.14 | 16 / 20 | |
| 2.22.13 | 16 / 20 | |
| 2.22.12 | 16 / 20 | |
| 2.22.11 | 16 / 20 | |
| 2.22.10 | 16 / 20 | |
| 2.22.9 | 16 / 20 | |
| 2.22.8 | 16 / 20 | |
| 2.22.7 | 16 / 20 | |
| 2.22.6 | 16 / 20 | |
| 2.22.4 | 17 / 19 | |
| 2.22.3 | 17 / 19 | |
| 2.22.2 | 17 / 19 | |
| 2.22.1 | 17 / 19 | |
| 2.22.0 | 17 / 19 | |
| 2.21.6 | 17 / 19 | |
| 2.21.5 | 17 / 19 | |
| 2.21.4 | 17 / 19 | |
| 2.21.3 | 17 / 19 | |
| 2.21.2 | 17 / 19 | |
| 2.21.1 | 17 / 19 | |
| 2.21.0 | 16 / 19 | |
| 2.20.35 | 17 / 19 | |
| 2.20.34 | 17 / 19 | |
| 2.20.16 | 16 / 19 |
v3.1.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dregop) than the most recent previously approved version (eraviart) on 2026-07-10, but dregop 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.
v3.1.22
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (eraviart) than the most recent previously approved version (dregop) on 2026-07-08, but eraviart 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.
v3.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dregop) than the most recent previously approved version (hboisgibault) on 2026-05-19, but dregop 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.
v3.1.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dregop) than the most recent previously approved version (hboisgibault) on 2026-05-04, but dregop 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.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-03-10, but hboisgibault 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.22.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-03-09, but hboisgibault 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.22.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-03-05, but hboisgibault 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.22.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-03-04, but hboisgibault 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.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-02-18, but hboisgibault 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.21.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-02-18, but hboisgibault 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.21.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hboisgibault) than the most recent previously approved version (dregop) on 2026-02-17, but hboisgibault 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.20.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dregop) than the most recent previously approved version (hboisgibault) on 2025-12-10, but dregop 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.