@breadstone/archipel-platform-authentication MIT 26 versions

@breadstone/archipel-platform-authentication

npm Repository Homepage

JWT and OAuth authentication, MFA, session management, and email verification for NestJS applications.

26

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ruederennes

Keywords

nestjsauthenticationjwtoauthmfapassportsessionarchipel

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@breadstone/archipel-platform-mailing	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/28
phantom-deps	phantom-dep:@breadstone/archipel-platform-openapi	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/28
phantom-deps	phantom-dep:@breadstone/archipel-platform-database	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/28
phantom-deps	phantom-dep:bcrypt	AI (phantom-deps): bcrypt is a native binding commonly referenced in config/factory files rather than direct imports; stable false positive for this package.	ai	2026/04/28
semgrep	semgrep:base64-decode	AI (semgrep): Used in MfaEncryptionService.decrypt() for AES-GCM IV/authTag extraction — standard crypto pattern, not obfuscation.	ai	2026/04/28

Versions (showing 26 of 26)

Version	Deps	Published
0.0.46	5 / 21	2026-06-03
0.0.45	5 / 21	2026-05-27
0.0.44	5 / 21	2026-05-27
0.0.43	5 / 21	2026-05-26
0.0.42	5 / 21	2026-05-26
0.0.41	5 / 21	2026-05-13
0.0.40	5 / 21	2026-05-10
0.0.39	5 / 21	2026-05-08
0.0.38	5 / 21	2026-05-08
0.0.37	5 / 21	2026-05-08
0.0.36	5 / 21	2026-05-04
0.0.35	5 / 21	2026-05-04
0.0.34	5 / 21	2026-05-04
0.0.33	5 / 21	2026-05-04
0.0.32	5 / 21	2026-04-26
0.0.31	5 / 21	2026-04-24
0.0.30	5 / 21	2026-04-24
0.0.28	5 / 21	2026-04-23
0.0.27	5 / 21	2026-04-23
0.0.26	5 / 21	2026-04-23
0.0.25	5 / 21	2026-04-23
0.0.24	5 / 21	2026-04-23
0.0.23	6 / 21	2026-04-22
0.0.22	6 / 21	2026-04-22
0.0.19	8 / 17	2026-04-21
0.0.1	23 / 8	2026-04-08

v0.0.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.45

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.