@accounts/common
Fullstack authentication and accounts-management
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from accounts to dotansimha occurred in 2017 as part of a known legitimate project transition; dotansimha has a strong track record and this is stable historical context for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.0.21 | 1 / 4 | |
| 0.0.20 | 1 / 4 | |
| 0.0.18 | 1 / 21 | |
| 0.0.16 | 1 / 21 | |
| 0.0.15 | 1 / 20 | |
| 0.0.13 | 1 / 20 | |
| 0.0.11 | 1 / 20 | |
| 0.0.10 | 1 / 20 | |
| 0.0.9 | 1 / 20 | |
| 0.0.7 | 1 / 18 | |
| 0.0.6 | 1 / 18 | |
| 0.0.5 | 1 / 18 | |
| 0.0.4 | 1 / 18 | |
| 0.0.3 | 2 / 17 | |
| 0.0.2 | 2 / 27 | |
| 0.0.1 | 2 / 27 |
v0.0.20
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
2 findingsThis version was published by a different npm account than previous versions on 2017-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.9
2 findingsThis version was published by a different npm account than previous versions on 2017-03-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.