@node-in-layers/auth
A Node In Layers Package, generated by the Node In Layers Toolkit.
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to deserialize a stored PBKDF2 hash for timingSafeEqual comparison — standard password verification, not payload hiding. | ai | |
| phantom-deps | phantom-dep:jwk-to-pem | AI (phantom-deps): jwk-to-pem is listed in dependencies in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 14 / 44 | |
| 1.2.14 | 14 / 44 | |
| 1.2.13 | 14 / 44 | |
| 1.2.12 | 14 / 44 | |
| 1.2.11 | 14 / 44 | |
| 1.2.10 | 14 / 44 | |
| 1.2.9 | 14 / 44 | |
| 1.2.8 | 14 / 44 | |
| 1.2.7 | 14 / 44 | |
| 1.2.6 | 14 / 44 | |
| 1.2.5 | 14 / 44 | |
| 1.2.4 | 14 / 44 | |
| 1.2.3 | 14 / 44 | |
| 1.2.2 | 14 / 44 | |
| 1.2.0 | 14 / 44 | |
| 1.1.1 | 14 / 44 | |
| 1.1.0 | 14 / 44 | |
| 1.0.4 | 12 / 44 | |
| 1.0.3 | 12 / 44 | |
| 1.0.2 | 12 / 44 | |
| 1.0.1 | 12 / 44 | |
| 1.0.0 | 9 / 44 |
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.