@majikah/majik-signature
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:pdf-lib | AI (phantom-deps): pdf-lib is declared in deps and used indirectly; stable FP for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fflate and pdf-lib are established, benign libraries appropriate for a document-signing package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Size increase consistent with adding pdf-lib/fflate support; no obfuscation or malware indicators. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth attributable to PDF and compression feature additions; no suspicious payloads detected. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.0.17 | 6 / 1 | |
| 0.0.16 | 6 / 1 | |
| 0.0.15 | 6 / 1 | |
| 0.0.14 | 6 / 1 | |
| 0.0.13 | 6 / 1 | |
| 0.0.12 | 6 / 1 | |
| 0.0.11 | 6 / 1 | |
| 0.0.10 | 6 / 1 | |
| 0.0.9 | 6 / 1 | |
| 0.0.8 | 6 / 1 | |
| 0.0.7 | 7 / 1 | |
| 0.0.6 | 6 / 0 | |
| 0.0.5 | 6 / 0 | |
| 0.0.4 | 6 / 0 | |
| 0.0.3 | 6 / 0 | |
| 0.0.2 | 6 / 0 | |
| 0.0.1 | 4 / 0 |
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.