@tricoteuses/legifrance
Library & tools to browse legal open data from French Direction de l'information légale et administrative (Dila)
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): slug is a well-known, low-risk utility; addition is benign for this package. | ai | |
| license | copyleft-license:AGPL-3.0-or-later | AI (license): Package is intentionally AGPL-3.0; stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with real repo; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:jsdom | AI (phantom-deps): jsdom is declared as a runtime dep in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.18.7 | 7 / 59 | |
| 0.18.6 | 7 / 65 | |
| 0.18.5 | 7 / 65 | |
| 0.18.4 | 6 / 66 | |
| 0.18.3 | 6 / 66 | |
| 0.18.2 | 6 / 66 | |
| 0.18.1 | 6 / 66 | |
| 0.18.0 | 6 / 66 | |
| 0.17.0 | 6 / 66 | |
| 0.16.0 | 6 / 66 | |
| 0.15.17 | 6 / 66 | |
| 0.15.16 | 6 / 66 | |
| 0.15.14 | 6 / 66 | |
| 0.15.13 | 6 / 66 | |
| 0.15.10 | 6 / 68 | |
| 0.15.8 | 6 / 68 | |
| 0.15.7 | 6 / 68 | |
| 0.15.6 | 5 / 69 | |
| 0.15.5 | 5 / 69 | |
| 0.15.4 | 5 / 69 | |
| 0.15.3 | 5 / 69 | |
| 0.15.2 | 5 / 69 | |
| 0.15.1 | 5 / 69 | |
| 0.14.0 | 5 / 66 | |
| 0.13.1 | 5 / 60 | |
| 0.13.0 | 5 / 60 |
v0.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.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.
v0.17.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.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.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.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.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.