unimodules-permissions-interface
An interface for permissions modules
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 tsapeta to brentvatne reflects a legitimate Expo team internal transition; both are known Expo core contributors. Stable for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 0 / 1 | |
| 6.1.0 | 0 / 1 | |
| 6.0.0 | 0 / 1 | |
| 5.4.0 | 0 / 1 | |
| 5.3.0 | 0 / 1 | |
| 5.2.1 | 0 / 1 | |
| 5.2.0 | 0 / 1 | |
| 5.1.0 | 0 / 1 | |
| 5.0.0 | 0 / 1 | |
| 4.0.0 | 0 / 0 | |
| 3.0.0 | 0 / 0 | |
| 2.0.1 | 0 / 0 | |
| 2.0.0 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v6.2.0
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 2021-05-03. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-03-10. 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.
v6.0.0
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 2021-01-15. This could indicate a legitimate maintainer transition or an account compromise.
v5.4.0
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 2020-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v5.3.0
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 2020-08-18. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
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 2020-05-27. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
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 2020-03-03. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.