@coopenomics/factory
Фабрика юридических документов кооператива
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Long Base64 string is Arial font data for PDF generation (ArialBase64 variable); stable false positive for this package. | ai | |
| source-diff | encoded-string-file:dist/index.mjs | AI (source-diff): Long Base64 string is Arial font data for PDF generation (ArialBase64 variable); stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:handlebars | AI (phantom-deps): Build/config-level reference pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Build/config-level reference pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:json-schema | AI (phantom-deps): Build/config-level reference pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:inline-css | AI (phantom-deps): Build/config-level reference pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:eosjs-ecc | AI (phantom-deps): Build/config-level reference pattern; stable for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2026.5.14 | 15 / 18 | |
| 2026.4.30 | 15 / 18 | |
| 2025.11.8 | 15 / 17 | |
| 2025.11.7 | 15 / 17 | |
| 2025.11.6 | 15 / 17 |
v2026.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.30
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.