@dynatrace/dtrum-api-types
Typescript types for the Dynatrace RUM JavaScript dtrum.* API
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Pure type-definition package; no executable code; provenance gap is low risk for this package. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 1.343.7 | 0 / 0 | |
| 1.343.6 | 0 / 0 | |
| 1.343.5 | 0 / 0 | |
| 1.343.4 | 0 / 0 | |
| 1.343.3 | 0 / 0 | |
| 1.341.4 | 0 / 0 | |
| 1.341.3 | 0 / 0 | |
| 1.341.2 | 0 / 0 | |
| 1.341.1 | 0 / 0 | |
| 1.339.9 | 0 / 0 | |
| 1.339.8 | 0 / 0 | |
| 1.339.7 | 0 / 0 | |
| 1.339.6 | 0 / 0 | |
| 1.339.5 | 0 / 0 | |
| 1.339.4 | 0 / 0 | |
| 1.339.3 | 0 / 0 | |
| 1.337.12 | 0 / 0 | |
| 1.337.11 | 0 / 0 | |
| 1.337.10 | 0 / 0 | |
| 1.337.9 | 0 / 0 | |
| 1.337.8 | 0 / 0 | |
| 1.337.7 | 0 / 0 | |
| 1.337.6 | 0 / 0 | |
| 1.337.5 | 0 / 0 | |
| 1.337.4 | 0 / 0 | |
| 1.337.3 | 0 / 0 | |
| 1.337.2 | 0 / 0 | |
| 1.337.1 | 0 / 0 | |
| 1.335.9 | 0 / 0 | |
| 1.335.7 | 0 / 0 | |
| 1.335.6 | 0 / 0 | |
| 1.335.5 | 0 / 0 | |
| 1.333.16 | 0 / 0 | |
| 1.333.12 | 0 / 0 | |
| 1.333.10 | 0 / 0 | |
| 1.333.4 | 0 / 0 | |
| 1.333.2 | 0 / 0 | |
| 1.331.9 | 0 / 0 | |
| 1.329.4 | 0 / 0 | |
| 1.327.2 | 0 / 0 | |
| 1.325.2 | 0 / 0 | |
| 1.325.1 | 0 / 0 | |
| 1.323.1 | 0 / 0 | |
| 1.321.4 | 0 / 0 | |
| 1.319.3 | 0 / 0 | |
| 1.317.5 | 0 / 0 | |
| 1.315.1 | 0 / 0 | |
| 1.313.2 | 0 / 0 | |
| 1.311.3 | 0 / 0 | |
| 1.309.4 | 0 / 0 | |
| 1.307.0 | 0 / 0 | |
| 1.305.2 | 0 / 0 | |
| 1.303.1 | 0 / 0 | |
| 1.301.7 | 0 / 0 | |
| 1.299.6 | 0 / 0 | |
| 1.297.3 | 0 / 0 | |
| 1.295.6 | 0 / 0 | |
| 1.293.12 | 0 / 0 | |
| 1.291.1 | 0 / 0 | |
| 1.289.2 | 0 / 0 | |
| 1.287.7 | 0 / 0 | |
| 1.285.2 | 0 / 0 |
v1.343.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.343.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.343.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.343.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.343.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.341.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.307.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.305.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.303.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.301.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.299.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.297.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.295.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.293.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.291.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.289.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.287.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.285.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.