@pactosigna/records
Generate audit-ready regulatory PDF records from PactoSigna-compliant git repositories
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used Markdown parser. Its use here is appropriate for PDF generation from Markdown content and poses no meaningful risk. | ai | |
| provenance | no-provenance | AI (provenance): Package is published via GitHub Actions CI with a legitimate repo URL; lack of Sigstore attestation is common and not a risk signal for this package. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.1.111 | 4 / 8 | |
| 0.1.110 | 4 / 8 | |
| 0.1.109 | 4 / 8 | |
| 0.1.108 | 4 / 8 | |
| 0.1.107 | 4 / 8 | |
| 0.1.105 | 4 / 8 | |
| 0.1.104 | 4 / 8 | |
| 0.1.103 | 4 / 8 | |
| 0.1.101 | 4 / 8 | |
| 0.1.100 | 4 / 8 | |
| 0.1.99 | 4 / 8 | |
| 0.1.98 | 4 / 8 | |
| 0.1.97 | 4 / 8 | |
| 0.1.96 | 4 / 8 | |
| 0.1.95 | 4 / 8 | |
| 0.1.94 | 4 / 8 | |
| 0.1.93 | 4 / 8 | |
| 0.1.92 | 4 / 8 | |
| 0.1.90 | 4 / 8 | |
| 0.1.88 | 4 / 8 | |
| 0.1.86 | 4 / 8 | |
| 0.1.85 | 4 / 8 | |
| 0.1.83 | 4 / 8 | |
| 0.1.82 | 4 / 8 | |
| 0.1.81 | 4 / 8 | |
| 0.1.79 | 4 / 8 | |
| 0.1.77 | 4 / 8 | |
| 0.1.76 | 4 / 8 | |
| 0.1.74 | 4 / 8 | |
| 0.1.73 | 4 / 8 | |
| 0.1.71 | 4 / 8 | |
| 0.1.65 | 4 / 8 | |
| 0.1.61 | 4 / 8 | |
| 0.1.59 | 4 / 8 | |
| 0.1.56 | 4 / 8 | |
| 0.1.54 | 4 / 8 | |
| 0.1.51 | 4 / 8 | |
| 0.1.49 | 4 / 8 | |
| 0.1.48 | 4 / 8 | |
| 0.1.44 | 4 / 8 | |
| 0.1.37 | 4 / 8 | |
| 0.1.34 | 4 / 8 | |
| 0.1.33 | 4 / 8 | |
| 0.1.31 | 4 / 8 | |
| 0.1.30 | 4 / 8 | |
| 0.1.26 | 4 / 8 | |
| 0.1.23 | 4 / 8 | |
| 0.1.22 | 4 / 8 | |
| 0.1.21 | 4 / 8 | |
| 0.1.18 | 4 / 8 | |
| 0.1.15 | 4 / 8 |
v0.1.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.71
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.1.65
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.1.61
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.1.59
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.1.56
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.1.54
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.1.51
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.1.49
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.1.48
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.1.44
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.1.37
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.1.34
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.1.33
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.1.31
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.1.30
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.1.26
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.1.23
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.1.22
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.1.21
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.1.18
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.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.