@zerodev/permissions
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
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 5.6.3 | 2 / 0 | |
| 5.6.2 | 2 / 0 | |
| 5.6.1 | 2 / 0 | |
| 5.6.0 | 2 / 0 | |
| 5.5.14 | 2 / 0 | |
| 5.5.13 | 2 / 0 | |
| 5.5.12 | 2 / 0 | |
| 5.5.11 | 2 / 0 | |
| 5.5.10 | 2 / 0 | |
| 5.5.9 | 2 / 0 | |
| 5.5.8 | 2 / 0 | |
| 5.5.7 | 2 / 0 | |
| 5.5.6 | 2 / 0 | |
| 5.5.5 | 2 / 0 | |
| 5.5.4 | 2 / 0 | |
| 5.5.3 | 2 / 0 | |
| 5.5.2 | 2 / 0 | |
| 5.5.1 | 2 / 0 | |
| 5.5.0 | 2 / 0 | |
| 5.4.10 | 2 / 0 | |
| 5.4.9 | 2 / 0 | |
| 5.4.8 | 2 / 0 | |
| 5.4.7 | 2 / 0 | |
| 5.4.6 | 2 / 0 | |
| 5.4.5 | 2 / 0 | |
| 5.4.4 | 2 / 0 | |
| 5.4.3 | 2 / 0 | |
| 5.4.2 | 2 / 0 | |
| 5.4.1 | 2 / 0 | |
| 5.4.0 | 2 / 0 | |
| 5.3.2 | 2 / 0 |
v5.5.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (justinzen) on 2025-06-18, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (justinzen) on 2025-05-24, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (justinzen) than the most recent previously approved version (leekt216) on 2025-05-19, but justinzen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (justinzen) than the most recent previously approved version (leekt216) on 2025-05-19, but justinzen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leekt216) than the most recent previously approved version (justinzen) on 2025-04-23, but leekt216 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (justinzen) than the most recent previously approved version (leekt216) on 2025-03-26, but justinzen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leekt216) than the most recent previously approved version (sahilvasava) on 2025-03-11, but leekt216 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-08-22, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sahilvasava) than the most recent previously approved version (adnpark) on 2024-07-26, but sahilvasava is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.