@mseva/digit-ui-module-pt
Property Tax Module
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared dependency; used indirectly via react-redux and react-query. | ai | |
| phantom-deps | phantom-dep:redux-thunk | AI (phantom-deps): Declared dependency; used indirectly via redux integration. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Declared dependency; used indirectly via @mseva/digit-ui-react-components. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): Build tool in dependencies; used in build scripts, not runtime code. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.0.40 | 13 / 0 | |
| 1.0.38 | 13 / 0 | |
| 1.0.37 | 13 / 0 | |
| 1.0.34 | 13 / 0 | |
| 1.0.32 | 13 / 0 | |
| 1.0.31 | 13 / 0 | |
| 1.0.30 | 13 / 0 | |
| 1.0.29 | 13 / 0 | |
| 1.0.28 | 13 / 0 | |
| 1.0.27 | 13 / 0 | |
| 1.0.26 | 13 / 0 | |
| 1.0.25 | 13 / 0 | |
| 1.0.23 | 13 / 0 | |
| 1.0.22 | 13 / 0 | |
| 1.0.21 | 13 / 0 | |
| 1.0.19 | 13 / 0 | |
| 1.0.18 | 13 / 0 | |
| 1.0.15 | 13 / 0 | |
| 1.0.13 | 13 / 0 |
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.