@rango-dev/queue-manager-rango-preset
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo with 331 versions; irregular publish cadence is expected for preset packages in this org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo preset package; sparse metadata is consistent across all @rango-dev packages in this registry. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.62.0 | 5 / 1 | |
| 0.61.1 | 4 / 1 | |
| 0.61.0 | 4 / 1 | |
| 0.60.0 | 4 / 1 | |
| 0.59.0 | 4 / 1 | |
| 0.58.0 | 4 / 1 | |
| 0.57.0 | 4 / 1 | |
| 0.56.1 | 4 / 1 | |
| 0.54.0 | 4 / 1 | |
| 0.53.0 | 3 / 1 | |
| 0.52.0 | 3 / 1 | |
| 0.51.0 | 3 / 1 | |
| 0.50.0 | 3 / 1 | |
| 0.49.0 | 3 / 1 | |
| 0.48.1 | 3 / 1 | |
| 0.48.0 | 3 / 1 | |
| 0.47.0 | 3 / 1 | |
| 0.46.0 | 3 / 1 | |
| 0.45.1 | 3 / 1 | |
| 0.45.0 | 3 / 1 | |
| 0.44.0 | 3 / 1 | |
| 0.43.0 | 3 / 1 | |
| 0.42.0 | 3 / 1 | |
| 0.41.0 | 3 / 1 | |
| 0.40.0 | 3 / 1 | |
| 0.39.0 | 3 / 1 | |
| 0.38.0 | 3 / 1 | |
| 0.37.0 | 3 / 1 | |
| 0.36.0 | 3 / 1 | |
| 0.35.1 | 3 / 1 | |
| 0.35.0 | 3 / 1 | |
| 0.34.0 | 4 / 1 | |
| 0.33.2 | 4 / 1 | |
| 0.33.1 | 4 / 1 | |
| 0.33.0 | 4 / 1 | |
| 0.1.14 | 2 / 1 | |
| 0.1.13 | 2 / 1 | |
| 0.1.12 | 2 / 1 | |
| 0.1.11 | 2 / 1 | |
| 0.1.10 | 2 / 1 |
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.