@contrail/flexplm
Library used for integration with flexplm.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Same-org publisher with long clean track record; likely internal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with internal team rotation, no behavior change accompanies it. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is same-scope first-party @contrail package, not third-party. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI upload command; child_process use is expected for a FlexPLM integration CLI tool. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-supplied mapping config file at runtime; standard plugin/config-loader pattern for this CLI. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @contrail-namespace library; sparse metadata is consistent with a private/org package, not spam. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.7.2 | 6 / 7 | |
| 1.7.1 | 6 / 7 | |
| 1.7.0 | 6 / 7 | |
| 1.6.1 | 6 / 7 | |
| 1.6.0 | 6 / 7 | |
| 1.5.0 | 6 / 7 | |
| 1.4.0 | 6 / 7 | |
| 1.3.2 | 6 / 7 | |
| 1.3.1 | 6 / 7 | |
| 1.3.0 | 6 / 7 | |
| 1.2.1 | 6 / 7 | |
| 1.2.0 | 6 / 7 | |
| 1.1.66 | 6 / 7 | |
| 1.1.65 | 7 / 7 | |
| 1.1.64 | 6 / 7 | |
| 1.1.63 | 6 / 7 | |
| 1.1.62 | 6 / 7 | |
| 1.1.61 | 6 / 7 | |
| 1.1.60 | 6 / 7 | |
| 1.1.59 | 5 / 7 | |
| 1.1.58 | 5 / 7 | |
| 1.1.57 | 5 / 7 | |
| 1.1.56 | 5 / 7 | |
| 1.1.55 | 5 / 7 | |
| 1.1.54 | 5 / 7 | |
| 1.1.53 | 5 / 7 | |
| 1.1.52 | 5 / 7 | |
| 1.1.51 | 5 / 7 | |
| 1.1.50 | 5 / 7 | |
| 1.1.49 | 5 / 7 | |
| 1.1.48 | 5 / 7 | |
| 1.1.47 | 5 / 7 | |
| 1.1.46 | 5 / 7 | |
| 1.1.45 | 5 / 7 | |
| 1.1.44 | 5 / 7 | |
| 1.1.43 | 5 / 7 | |
| 1.1.42 | 5 / 7 | |
| 1.1.41 | 5 / 7 | |
| 1.1.40 | 5 / 7 | |
| 1.1.39 | 5 / 7 | |
| 1.1.37 | 5 / 7 | |
| 1.1.36 | 5 / 7 | |
| 1.1.35 | 5 / 7 | |
| 1.1.34 | 5 / 7 | |
| 1.1.33 | 5 / 7 | |
| 1.1.32 | 5 / 7 | |
| 1.1.31 | 5 / 7 | |
| 1.1.30 | 5 / 7 | |
| 1.1.29 | 5 / 7 | |
| 1.1.28 | 5 / 7 | |
| 1.1.27 | 5 / 7 | |
| 1.1.26 | 5 / 7 | |
| 1.1.25 | 5 / 7 | |
| 1.1.24 | 5 / 7 | |
| 1.1.23 | 5 / 7 | |
| 1.1.22 | 5 / 7 | |
| 1.1.21 | 5 / 7 | |
| 1.1.20 | 5 / 7 | |
| 1.1.19 | 5 / 7 | |
| 1.1.18 | 5 / 7 | |
| 1.1.17 | 5 / 7 | |
| 1.1.16 | 5 / 7 | |
| 1.1.15 | 5 / 7 | |
| 1.1.14 | 5 / 7 | |
| 1.1.13 | 5 / 7 | |
| 1.1.12 | 5 / 7 | |
| 1.1.11 | 5 / 7 | |
| 1.1.10 | 5 / 7 | |
| 1.1.9 | 5 / 7 | |
| 1.1.8 | 5 / 7 | |
| 1.1.7 | 5 / 7 | |
| 1.1.6 | 5 / 7 | |
| 1.1.5 | 5 / 7 | |
| 1.1.4 | 5 / 7 | |
| 1.1.3 | 5 / 7 | |
| 1.1.2 | 5 / 7 | |
| 1.0.19 | 5 / 7 | |
| 1.0.18 | 5 / 7 | |
| 1.0.17 | 5 / 7 | |
| 1.0.16 | 5 / 7 | |
| 1.0.15 | 5 / 7 | |
| 1.0.14 | 5 / 7 | |
| 1.0.13 | 5 / 7 | |
| 1.0.12 | 5 / 7 | |
| 1.0.9 | 5 / 7 | |
| 1.0.8 | 5 / 7 | |
| 1.0.7 | 5 / 7 | |
| 1.0.6 | 5 / 7 | |
| 1.0.5 | 4 / 7 | |
| 1.0.4 | 1 / 7 | |
| 1.0.3 | 1 / 7 | |
| 1.0.2 | 1 / 7 | |
| 1.0.1 | 1 / 7 | |
| 1.0.0 | 1 / 7 |
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
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 (chris_vibeiq) than the most recent previously approved version (btosadoprater) on 2023-09-12, but chris_vibeiq 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.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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 (btosadoprater) than the most recent previously approved version (kamalvibeiq) on 2023-08-16, but btosadoprater 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.
v1.0.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 (btosadoprater) than the most recent previously approved version (kamalvibeiq) on 2023-08-16, but btosadoprater 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.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (brian.lindauer) on 2022-04-30. It has since remained available on npm for 1549 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.