@maroonedsoftware/authentication
Authentication utilities for ServerKit.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): @maroonedsoftware uses 0.0.0 as a legitimate initial version across their scoped package ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual (knoxcoder) to GitHub Actions CI/CD with SLSA provenance attestation; legitimate automation handoff. | ai | |
| phantom-deps | phantom-dep:arctic | AI (phantom-deps): arctic is a legitimate OAuth provider library; phantom-dep heuristic fires because it's re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:zxcvbn-ts | AI (phantom-deps): zxcvbn-ts is a password strength library used alongside @zxcvbn-ts/* scoped packages; phantom-dep is a false positive here. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 4.28.0 | 21 / 5 | |
| 4.27.2 | 21 / 5 | |
| 4.27.1 | 21 / 5 | |
| 4.27.0 | 21 / 5 | |
| 4.26.0 | 21 / 5 | |
| 4.25.0 | 21 / 5 | |
| 4.24.0 | 21 / 5 | |
| 4.23.0 | 21 / 5 | |
| 4.22.2 | 21 / 5 | |
| 4.22.1 | 21 / 5 | |
| 4.22.0 | 21 / 5 | |
| 4.21.2 | 21 / 5 | |
| 4.21.1 | 21 / 5 | |
| 4.21.0 | 21 / 5 | |
| 4.20.0 | 21 / 5 | |
| 4.19.0 | 21 / 5 | |
| 4.18.1 | 21 / 5 | |
| 4.18.0 | 21 / 5 | |
| 4.17.0 | 21 / 5 | |
| 4.16.0 | 21 / 5 | |
| 4.15.0 | 21 / 5 | |
| 4.14.0 | 21 / 5 | |
| 4.13.0 | 21 / 5 | |
| 4.12.0 | 20 / 5 | |
| 4.11.0 | 20 / 5 | |
| 4.10.0 | 20 / 5 | |
| 4.9.0 | 20 / 5 | |
| 4.8.0 | 20 / 5 | |
| 4.7.0 | 20 / 5 | |
| 4.6.0 | 20 / 5 | |
| 4.5.1 | 20 / 5 | |
| 4.5.0 | 20 / 5 | |
| 4.4.1 | 20 / 5 | |
| 4.4.0 | 20 / 5 | |
| 4.3.0 | 20 / 5 | |
| 4.2.0 | 19 / 5 | |
| 4.1.0 | 19 / 5 | |
| 4.0.0 | 19 / 5 | |
| 3.0.0 | 19 / 5 | |
| 2.3.0 | 19 / 5 | |
| 2.2.1 | 19 / 5 | |
| 2.2.0 | 19 / 5 | |
| 2.1.0 | 19 / 5 | |
| 2.0.0 | 19 / 5 | |
| 1.1.0 | 19 / 5 | |
| 1.0.0 | 19 / 5 | |
| 0.23.0 | 19 / 5 | |
| 0.22.0 | 17 / 5 | |
| 0.21.0 | 17 / 5 | |
| 0.20.0 | 17 / 5 | |
| 0.19.0 | 17 / 5 |
v4.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.27.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.22.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.21.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.