@escapenavigator/services
// полезные
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package with consistent publish history; lack of Sigstore provenance is a process gap, not a security signal here. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Library dependency referenced in config/type declarations; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:date-fns-tz | AI (phantom-deps): Library dependency referenced in config/type declarations; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:class-transformer | AI (phantom-deps): Internal monorepo package; deps declared for peer/config use, not direct import. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Internal monorepo package; deps declared for peer/config use, not direct import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package; missing repo/readme/keywords is consistent across all 380 versions. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Internal monorepo package; deps declared for peer/config use, not direct import. | ai | |
| phantom-deps | phantom-dep:class-validator | AI (phantom-deps): Internal monorepo package; deps declared for peer/config use, not direct import. | ai |
Versions (showing 37 of 142)
| Version | Deps | Published |
|---|---|---|
| 1.10.36 | 10 / 15 | |
| 1.10.35 | 10 / 15 | |
| 1.10.34 | 10 / 15 | |
| 1.10.33 | 10 / 15 | |
| 1.10.31 | 10 / 15 | |
| 1.10.30 | 10 / 15 | |
| 1.10.29 | 10 / 15 | |
| 1.10.28 | 10 / 15 | |
| 1.10.26 | 10 / 15 | |
| 1.10.25 | 10 / 15 | |
| 1.10.24 | 10 / 15 | |
| 1.10.20 | 10 / 15 | |
| 1.10.19 | 10 / 15 | |
| 1.10.18 | 10 / 15 | |
| 1.10.17 | 10 / 15 | |
| 1.10.16 | 10 / 15 | |
| 1.10.15 | 10 / 15 | |
| 1.10.14 | 10 / 15 | |
| 1.10.13 | 10 / 15 | |
| 1.10.12 | 10 / 15 | |
| 1.10.11 | 10 / 15 | |
| 1.10.10 | 10 / 15 | |
| 1.10.9 | 10 / 15 | |
| 1.10.8 | 10 / 15 | |
| 1.10.7 | 10 / 15 | |
| 1.10.6 | 10 / 15 | |
| 1.10.5 | 10 / 15 | |
| 1.10.4 | 10 / 15 | |
| 1.10.3 | 10 / 15 | |
| 1.10.2 | 10 / 15 | |
| 1.10.1 | 10 / 15 | |
| 1.10.0 | 10 / 15 | |
| 1.9.50 | 10 / 15 | |
| 1.9.49 | 10 / 15 | |
| 1.9.48 | 10 / 15 | |
| 1.9.47 | 10 / 15 | |
| 1.9.46 | 10 / 15 |
v1.10.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.