@drax/identity-back
Identity module for user management, authentication and authorization.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@drax/crud-back | AI (dependencies): Internal @drax monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@drax/email-back | AI (dependencies): Internal @drax monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@drax/common-back | AI (dependencies): Internal @drax monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@drax/identity-share | AI (dependencies): Internal @drax monorepo sibling; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established @drax ecosystem package; no provenance across all 169 versions, consistent pattern not a new risk. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 3.51.0 | 8 / 11 | |
| 3.50.0 | 8 / 11 | |
| 3.48.0 | 8 / 11 | |
| 3.46.0 | 8 / 11 | |
| 3.39.0 | 8 / 11 | |
| 3.36.0 | 8 / 11 | |
| 3.32.0 | 8 / 11 | |
| 3.29.0 | 8 / 11 | |
| 3.28.0 | 8 / 11 | |
| 3.27.0 | 8 / 11 | |
| 3.26.0 | 8 / 11 | |
| 3.23.0 | 8 / 11 | |
| 3.21.0 | 8 / 11 | |
| 3.20.0 | 8 / 11 | |
| 3.19.0 | 8 / 11 | |
| 3.18.0 | 8 / 11 | |
| 3.17.3 | 8 / 11 | |
| 3.17.2 | 8 / 11 | |
| 3.17.0 | 8 / 11 | |
| 3.15.0 | 8 / 11 | |
| 3.14.0 | 8 / 11 | |
| 3.13.0 | 8 / 11 | |
| 3.12.0 | 8 / 11 | |
| 3.11.0 | 8 / 11 | |
| 3.10.0 | 8 / 11 | |
| 3.9.0 | 8 / 11 | |
| 3.6.0 | 8 / 11 | |
| 3.5.1 | 8 / 11 | |
| 3.5.0 | 8 / 11 | |
| 3.4.2 | 8 / 11 | |
| 3.4.1 | 8 / 11 | |
| 3.2.0 | 8 / 11 | |
| 3.1.0 | 8 / 11 | |
| 3.0.0 | 8 / 11 | |
| 2.11.0 | 8 / 11 | |
| 2.9.0 | 8 / 11 | |
| 2.8.0 | 8 / 11 | |
| 2.6.0 | 8 / 11 | |
| 2.4.0 | 8 / 11 | |
| 2.3.0 | 8 / 11 | |
| 2.1.1 | 8 / 11 | |
| 2.0.2 | 8 / 11 | |
| 2.0.1 | 8 / 11 | |
| 2.0.0 | 8 / 11 | |
| 1.4.1 | 8 / 11 | |
| 1.4.0 | 8 / 11 | |
| 1.3.1 | 8 / 11 | |
| 1.3.0 | 8 / 11 | |
| 1.1.1 | 8 / 11 |
v3.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.