@tricoteuses/assemblee
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:command-line-args | AI (phantom-deps): CLI utility deps used via config/scripts, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:command-line-usage | AI (phantom-deps): Same as command-line-args; CLI helper used indirectly via scripts. | ai | |
| phantom-deps | phantom-dep:p-limit | AI (phantom-deps): Declared dep used in async scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Declared dep used in data scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): Declared runtime dep used in image processing scripts; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-stream-zip | AI (phantom-deps): Declared dep used in zip handling scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:deep-object-diff | AI (phantom-deps): Declared dep used in data diff scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:fast-xml-parser | AI (phantom-deps): Declared dep used in XML parsing scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:cheerio | AI (phantom-deps): Declared dep used in HTML parsing scripts; stable false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.2.5 | 15 / 22 | |
| 3.2.4 | 15 / 22 | |
| 3.2.3 | 15 / 22 | |
| 3.2.2 | 15 / 22 | |
| 3.2.1 | 15 / 22 | |
| 2.5.18 | 15 / 24 | |
| 2.5.17 | 15 / 24 | |
| 2.5.16 | 15 / 24 | |
| 2.5.15 | 15 / 24 | |
| 2.5.11 | 15 / 24 | |
| 2.5.10 | 15 / 24 | |
| 2.5.8 | 15 / 24 | |
| 2.5.7 | 15 / 24 | |
| 2.5.6 | 15 / 24 | |
| 2.5.5 | 15 / 24 | |
| 2.5.4 | 15 / 24 | |
| 2.5.3 | 15 / 24 | |
| 2.5.2 | 15 / 24 | |
| 2.5.1 | 15 / 24 | |
| 2.5.0 | 15 / 24 |
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
2 findingsThis version was published by a different npm account than previous versions on 2025-11-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.