@pactosigna/schemas
Zod schemas, types, and constants for PactoSigna QMS document validation (ISO 13485)
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:@pactosigna/shared | AI (dependencies): Sibling monorepo package from the same @pactosigna org; workspace:* is a standard monorepo pattern and not an external risk. | ai | |
| dependencies | unvetted-dep:@pactosigna/contracts | AI (dependencies): This is a sibling workspace package in the same @pactosigna monorepo; workspace:* is a standard monorepo pattern and not a supply-chain risk. | ai |
Versions (showing 51 of 122)
| Version | Deps | Published |
|---|---|---|
| 0.1.123 | 2 / 5 | |
| 0.1.122 | 2 / 5 | |
| 0.1.121 | 2 / 5 | |
| 0.1.120 | 2 / 5 | |
| 0.1.119 | 2 / 5 | |
| 0.1.118 | 2 / 5 | |
| 0.1.117 | 2 / 5 | |
| 0.1.116 | 2 / 5 | |
| 0.1.115 | 2 / 5 | |
| 0.1.114 | 2 / 5 | |
| 0.1.113 | 2 / 5 | |
| 0.1.112 | 2 / 5 | |
| 0.1.111 | 2 / 5 | |
| 0.1.110 | 2 / 5 | |
| 0.1.109 | 2 / 5 | |
| 0.1.108 | 2 / 5 | |
| 0.1.107 | 2 / 5 | |
| 0.1.106 | 2 / 5 | |
| 0.1.105 | 2 / 5 | |
| 0.1.104 | 2 / 5 | |
| 0.1.103 | 2 / 5 | |
| 0.1.102 | 2 / 5 | |
| 0.1.101 | 2 / 5 | |
| 0.1.100 | 2 / 5 | |
| 0.1.99 | 2 / 5 | |
| 0.1.98 | 2 / 5 | |
| 0.1.97 | 2 / 5 | |
| 0.1.96 | 2 / 5 | |
| 0.1.95 | 2 / 5 | |
| 0.1.94 | 2 / 5 | |
| 0.1.93 | 2 / 5 | |
| 0.1.92 | 2 / 5 | |
| 0.1.91 | 2 / 5 | |
| 0.1.90 | 2 / 5 | |
| 0.1.89 | 2 / 5 | |
| 0.1.88 | 2 / 5 | |
| 0.1.87 | 2 / 5 | |
| 0.1.86 | 2 / 5 | |
| 0.1.85 | 2 / 5 | |
| 0.1.84 | 2 / 5 | |
| 0.1.83 | 2 / 5 | |
| 0.1.82 | 2 / 5 | |
| 0.1.81 | 2 / 5 | |
| 0.1.80 | 2 / 5 | |
| 0.1.79 | 2 / 5 | |
| 0.1.78 | 2 / 5 | |
| 0.1.77 | 2 / 5 | |
| 0.1.76 | 2 / 5 | |
| 0.1.75 | 2 / 5 | |
| 0.1.74 | 2 / 5 | |
| 0.1.73 | 2 / 5 |
v0.1.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.