@tezos-domains/core
Base library for interacting with tezos domains smart contracts.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/core.es2020.js | AI (source-diff): Rollup-bundled ES2020 output with readable code, not true obfuscation. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale ownership change from 2021, long-standing and non-adversarial, publisher trusted. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same historical maintainer change, already vetted context. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Old dormancy gap unrelated to current release; no malicious diff. | ai | |
| phantom-deps | phantom-dep:idna-uts46-hx | AI (phantom-deps): Declared runtime dependency used in build/config; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:lodash.isplainobject | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @tezos-domains/core is a legitimate Tezos Domains library; Levenshtein match to 'cors' is coincidental. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.34.1 | 2 / 17 | |
| 1.34.0 | 2 / 17 | |
| 1.33.1 | 2 / 17 | |
| 1.33.0 | 2 / 17 | |
| 1.32.0 | 2 / 17 | |
| 1.31.0 | 2 / 17 | |
| 1.30.2 | 2 / 17 | |
| 1.30.1 | 2 / 17 | |
| 1.30.0 | 2 / 17 | |
| 1.29.0 | 2 / 17 | |
| 1.28.0 | 2 / 17 | |
| 1.27.0 | 2 / 17 | |
| 1.26.0 | 2 / 14 | |
| 1.25.1 | 1 / 13 | |
| 1.25.0 | 1 / 13 | |
| 1.24.0 | 1 / 13 | |
| 1.23.0 | 1 / 13 | |
| 1.22.0 | 1 / 13 | |
| 1.21.0 | 1 / 13 | |
| 1.20.0 | 1 / 13 | |
| 1.19.0 | 1 / 13 | |
| 1.18.1 | 1 / 13 | |
| 1.18.0 | 1 / 13 | |
| 1.17.1 | 1 / 13 | |
| 1.17.0 | 1 / 13 | |
| 1.16.0 | 1 / 13 | |
| 1.15.0 | 1 / 13 | |
| 1.14.0 | 1 / 13 | |
| 1.13.1 | 1 / 13 | |
| 1.13.0 | 1 / 13 | |
| 1.12.0 | 1 / 13 | |
| 1.11.0 | 1 / 13 | |
| 1.10.0 | 1 / 13 | |
| 1.9.0 | 1 / 13 | |
| 1.8.0 | 1 / 13 | |
| 1.7.0 | 1 / 13 | |
| 1.6.0 | 1 / 13 | |
| 1.5.0 | 1 / 13 | |
| 1.4.0 | 1 / 13 | |
| 1.3.0 | 1 / 13 | |
| 1.2.0 | 1 / 13 | |
| 1.1.0 | 1 / 13 | |
| 1.0.0 | 1 / 13 |
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2024-04-20. It has since remained available on npm for 826 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2024-02-13. It has since remained available on npm for 892 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2023-06-21. It has since remained available on npm for 1130 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2023-06-12. It has since remained available on npm for 1139 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2023-05-08. It has since remained available on npm for 1174 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2023-02-07. It has since remained available on npm for 1263 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-12-21. It has since remained available on npm for 1311 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-11-29. It has since remained available on npm for 1333 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-10-09. It has since remained available on npm for 1384 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-09-16. It has since remained available on npm for 1407 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-08-31. It has since remained available on npm for 1423 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-08-18. It has since remained available on npm for 1436 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-07-06. It has since remained available on npm for 1479 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-06-15. It has since remained available on npm for 1500 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-06-14. It has since remained available on npm for 1501 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-06-13. It has since remained available on npm for 1502 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-06-07. It has since remained available on npm for 1509 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-05-31. It has since remained available on npm for 1515 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-04-11. It has since remained available on npm for 1566 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-04-09. It has since remained available on npm for 1567 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-03-02. It has since remained available on npm for 1605 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2022-01-20. It has since remained available on npm for 1647 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2021-12-28. It has since remained available on npm for 1669 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.