@steedos/accounts
Fullstack authentication and accounts-management for steedos.
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:shady-links-raw-ip | AI (semgrep): Raw IP is a localhost fallback default overridden by ROOT_URL env var; not a network exfiltration risk. | ai | |
| phantom-deps | phantom-dep:mem | AI (phantom-deps): Framework-level dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pug | AI (phantom-deps): Template engine loaded by convention in this framework package. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Middleware loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:csurf | AI (phantom-deps): Middleware loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Config parsing dep loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:url-join | AI (phantom-deps): Utility loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:app-root-path | AI (phantom-deps): Path utility loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package loaded by convention; stable false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.0.14 | 29 / 0 | |
| 3.0.13 | 29 / 0 | |
| 3.0.12 | 29 / 0 | |
| 3.0.11 | 29 / 0 | |
| 3.0.10 | 29 / 0 | |
| 3.0.9 | 29 / 0 | |
| 3.0.8 | 29 / 0 | |
| 3.0.7 | 29 / 0 | |
| 3.0.6 | 29 / 0 | |
| 3.0.4 | 29 / 0 | |
| 3.0.3 | 32 / 0 | |
| 3.0.2 | 32 / 0 | |
| 3.0.1 | 32 / 0 | |
| 3.0.0 | 32 / 0 | |
| 2.7.32 | 30 / 11 | |
| 2.7.31 | 30 / 11 | |
| 2.7.30 | 30 / 11 | |
| 2.7.29 | 30 / 11 | |
| 2.7.28 | 30 / 11 | |
| 2.7.27 | 30 / 11 | |
| 2.7.25 | 30 / 11 | |
| 2.7.24 | 30 / 11 | |
| 2.7.23 | 30 / 11 |
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.